Result for 1760FBC60C71D1CE1ADBC331627D1B872CBFAAC4

Query result

Key Value
FileName./opt/rh/rh-perl530/root/usr/share/doc/rh-perl530-perl-File-ShareDir-1.116/README.md
FileSize11462
MD5C2042A54640DB86DBE11294C4B6DB92D
SHA-11760FBC60C71D1CE1ADBC331627D1B872CBFAAC4
SHA-25622E1E5B99D9E2B6021A245154126AD8DE26CDADFD26D17465A92DA79E0158507
SSDEEP192:xArR0BZ4m+YQI1eIBdxfJHwmXLxCwmPLxC9mr49ue0YN/QTDhDGu:xcuymHQI1eIBdhJHwmXLgwmPLg9mr49k
TLSHT10D32852736E43337155247A1FB4F2099AB43D0EF15592228B88C85982F26B325AFF5ED
hashlookup:parent-total19
hashlookup:trust100

Network graph view

Parents (Total: 19)

The searched file hash is included in 19 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
MD59F6916AEE96E99C7D46A56A0D13DF846
PackageArchnoarch
PackageDescriptionThe intent of File::ShareDir is to provide a companion to Class::Inspector and File::HomeDir, modules that take a process that is well-known by advanced Perl developers but gets a little tricky, and make it more available to the larger Perl community. Quite often you want or need your Perl module (CPAN or otherwise) to have access to a large amount of read-only data that is stored on the file-system at run-time. On a linux-like system, this would be in a place such as /usr/share, however Perl runs on a wide variety of different systems, and so the use of any one location is unreliable. Perl provides a little-known method for doing this, but almost nobody is aware that it exists. As a result, module authors often go through some very strange ways to make the data available to their code. The most common of these is to dump the data out to an enormous Perl data structure and save it into the module itself. The result are enormous multi-megabyte .pm files that chew up a lot of memory needlessly. Another method is to put the data "file" after the __DATA__ compiler tag and limit yourself to access as a filehandle. The problem to solve is really quite simple. 1. Write the data files to the system at install time. 2. Know where you put them at run-time. Perl's install system creates an "auto" directory for both every distribution and for every module file. These are used by a couple of different auto-loading systems to store code fragments generated at install time, and various other modules written by the Perl "ancient masters". But the same mechanism is available to any dist or module to store any sort of data.
PackageNameperl-File-ShareDir
PackageReleaselp153.33.12
PackageVersion1.118
SHA-102E9ECA84EA8DE5D3D7C1A6B8CACD5019ED0213C
SHA-256B29F41CAA5BB10C68759C51AA44F55D17658F636BBC88174474DFA147DFE999D
Key Value
MD5D435B0E64EB2961B7BA5D133E55A9218
PackageArchnoarch
PackageDescriptionThe intent of File::ShareDir is to provide a companion to Class::Inspector and File::HomeDir, modules that take a process that is well-known by advanced Perl developers but gets a little tricky, and make it more available to the larger Perl community. Quite often you want or need your Perl module (CPAN or otherwise) to have access to a large amount of read-only data that is stored on the file-system at run-time. On a linux-like system, this would be in a place such as /usr/share, however Perl runs on a wide variety of different systems, and so the use of any one location is unreliable. Perl provides a little-known method for doing this, but almost nobody is aware that it exists. As a result, module authors often go through some very strange ways to make the data available to their code. The most common of these is to dump the data out to an enormous Perl data structure and save it into the module itself. The result are enormous multi-megabyte .pm files that chew up a lot of memory needlessly. Another method is to put the data "file" after the __DATA__ compiler tag and limit yourself to access as a filehandle. The problem to solve is really quite simple. 1. Write the data files to the system at install time. 2. Know where you put them at run-time. Perl's install system creates an "auto" directory for both every distribution and for every module file. These are used by a couple of different auto-loading systems to store code fragments generated at install time, and various other modules written by the Perl "ancient masters". But the same mechanism is available to any dist or module to store any sort of data.
PackageNameperl-File-ShareDir
PackageReleaselp150.33.1
PackageVersion1.118
SHA-116E1F45793DCF02B84B56D19E12AAE9EABEC3853
SHA-25666AFBBC72A8A19E45D30353DE7868D14D428A08473A9872E9F5A68C0E1FF3915
Key Value
MD591D5039738B75C25A9AC62F09E6FC63D
PackageArchnoarch
PackageDescriptionThe intent of File::ShareDir is to provide a companion to Class::Inspector and File::HomeDir, modules that take a process that is well-known by advanced Perl developers but gets a little tricky, and make it more available to the larger Perl community. Quite often you want or need your Perl module (CPAN or otherwise) to have access to a large amount of read-only data that is stored on the file-system at run-time. On a linux-like system, this would be in a place such as /usr/share, however Perl runs on a wide variety of different systems, and so the use of any one location is unreliable. Perl provides a little-known method for doing this, but almost nobody is aware that it exists. As a result, module authors often go through some very strange ways to make the data available to their code. The most common of these is to dump the data out to an enormous Perl data structure and save it into the module itself. The result are enormous multi-megabyte .pm files that chew up a lot of memory needlessly. Another method is to put the data "file" after the __DATA__ compiler tag and limit yourself to access as a filehandle. The problem to solve is really quite simple. 1. Write the data files to the system at install time. 2. Know where you put them at run-time. Perl's install system creates an "auto" directory for both every distribution and for every module file. These are used by a couple of different auto-loading systems to store code fragments generated at install time, and various other modules written by the Perl "ancient masters". But the same mechanism is available to any dist or module to store any sort of data.
PackageNameperl-File-ShareDir
PackageRelease1.3
PackageVersion1.118
SHA-12FCA69E7C6F3C9273001550022CCAC855EAD6616
SHA-256D8499FE5CD64B286D23006B5353882E49EADC0467D2E8389D91AC6534FF58ACA
Key Value
MD50254F9B04F1A8E4DB065698F892EF04D
PackageArchnoarch
PackageDescriptionThe intent of File::ShareDir is to provide a companion to Class::Inspector and File::HomeDir, modules that take a process that is well-known by advanced Perl developers but gets a little tricky, and make it more available to the larger Perl community.
PackageMaintainerFedora Project
PackageNameperl-File-ShareDir
PackageRelease2.fc34
PackageVersion1.118
SHA-140021CCAAB4CF4B704AD4F67390CAA4CB8386752
SHA-256696CAAAEF429D308D8FDE2CBDBF6656B1072EAFC3D3699196C90F59617DA464F
Key Value
MD562847331D48D2AFD9D99781CAB22FA3F
PackageArchnoarch
PackageDescriptionThe intent of File::ShareDir is to provide a companion to Class::Inspector and File::HomeDir, modules that take a process that is well-known by advanced Perl developers but gets a little tricky, and make it more available to the larger Perl community. Quite often you want or need your Perl module (CPAN or otherwise) to have access to a large amount of read-only data that is stored on the file-system at run-time. On a linux-like system, this would be in a place such as /usr/share, however Perl runs on a wide variety of different systems, and so the use of any one location is unreliable. Perl provides a little-known method for doing this, but almost nobody is aware that it exists. As a result, module authors often go through some very strange ways to make the data available to their code. The most common of these is to dump the data out to an enormous Perl data structure and save it into the module itself. The result are enormous multi-megabyte .pm files that chew up a lot of memory needlessly. Another method is to put the data "file" after the __DATA__ compiler tag and limit yourself to access as a filehandle. The problem to solve is really quite simple. 1. Write the data files to the system at install time. 2. Know where you put them at run-time. Perl's install system creates an "auto" directory for both every distribution and for every module file. These are used by a couple of different auto-loading systems to store code fragments generated at install time, and various other modules written by the Perl "ancient masters". But the same mechanism is available to any dist or module to store any sort of data.
PackageNameperl-File-ShareDir
PackageRelease33.2
PackageVersion1.118
SHA-14D00EFDEB5B2E343308ED01E2F0E46B9BA79F470
SHA-2563FE1441B8140B1826AAB615815F0F9B80A33A7D0948AD761999E026B86CB9E4F
Key Value
MD540E11260D1D4361081C7F400AA3369F0
PackageArchnoarch
PackageDescriptionThe intent of File::ShareDir is to provide a companion to Class::Inspector and File::HomeDir, modules that take a process that is well-known by advanced Perl developers but gets a little tricky, and make it more available to the larger Perl community. Quite often you want or need your Perl module (CPAN or otherwise) to have access to a large amount of read-only data that is stored on the file-system at run-time. On a linux-like system, this would be in a place such as /usr/share, however Perl runs on a wide variety of different systems, and so the use of any one location is unreliable. Perl provides a little-known method for doing this, but almost nobody is aware that it exists. As a result, module authors often go through some very strange ways to make the data available to their code. The most common of these is to dump the data out to an enormous Perl data structure and save it into the module itself. The result are enormous multi-megabyte .pm files that chew up a lot of memory needlessly. Another method is to put the data "file" after the __DATA__ compiler tag and limit yourself to access as a filehandle. The problem to solve is really quite simple. 1. Write the data files to the system at install time. 2. Know where you put them at run-time. Perl's install system creates an "auto" directory for both every distribution and for every module file. These are used by a couple of different auto-loading systems to store code fragments generated at install time, and various other modules written by the Perl "ancient masters". But the same mechanism is available to any dist or module to store any sort of data.
PackageNameperl-File-ShareDir
PackageRelease33.1
PackageVersion1.118
SHA-14D9780830D0CE604C0C1DD56A1B5BE07A91B3163
SHA-256248D52E502AA1A28A7908433C7BE8886E0D71204DD5E0E5395B7395B4DF4F90B
Key Value
MD53B881C3193DF170FF38B792ADB22BC16
PackageArchnoarch
PackageDescriptionThe intent of File::ShareDir is to provide a companion to Class::Inspector and File::HomeDir, modules that take a process that is well-known by advanced Perl developers but gets a little tricky, and make it more available to the larger Perl community. Quite often you want or need your Perl module (CPAN or otherwise) to have access to a large amount of read-only data that is stored on the file-system at run-time. On a linux-like system, this would be in a place such as /usr/share, however Perl runs on a wide variety of different systems, and so the use of any one location is unreliable. Perl provides a little-known method for doing this, but almost nobody is aware that it exists. As a result, module authors often go through some very strange ways to make the data available to their code. The most common of these is to dump the data out to an enormous Perl data structure and save it into the module itself. The result are enormous multi-megabyte .pm files that chew up a lot of memory needlessly. Another method is to put the data "file" after the __DATA__ compiler tag and limit yourself to access as a filehandle. The problem to solve is really quite simple. 1. Write the data files to the system at install time. 2. Know where you put them at run-time. Perl's install system creates an "auto" directory for both every distribution and for every module file. These are used by a couple of different auto-loading systems to store code fragments generated at install time, and various other modules written by the Perl "ancient masters". But the same mechanism is available to any dist or module to store any sort of data.
PackageNameperl-File-ShareDir
PackageRelease3.1
PackageVersion1.118
SHA-1569C88CEF815A93268BC7477DE9E006B3AFE0EC9
SHA-2568D754C624EF74C13E08AFE7CF9B6F1AC9E49FAAA0170FC5A0CE4671297BE4941
Key Value
MD5C240F70D5F95C0F301BED394B22B572B
PackageArchnoarch
PackageDescriptionThe intent of File::ShareDir is to provide a companion to Class::Inspector and File::HomeDir, modules that take a process that is well-known by advanced Perl developers but gets a little tricky, and make it more available to the larger Perl community. Quite often you want or need your Perl module (CPAN or otherwise) to have access to a large amount of read-only data that is stored on the file-system at run-time. On a linux-like system, this would be in a place such as /usr/share, however Perl runs on a wide variety of different systems, and so the use of any one location is unreliable. Perl provides a little-known method for doing this, but almost nobody is aware that it exists. As a result, module authors often go through some very strange ways to make the data available to their code. The most common of these is to dump the data out to an enormous Perl data structure and save it into the module itself. The result are enormous multi-megabyte .pm files that chew up a lot of memory needlessly. Another method is to put the data "file" after the __DATA__ compiler tag and limit yourself to access as a filehandle. The problem to solve is really quite simple. 1. Write the data files to the system at install time. 2. Know where you put them at run-time. Perl's install system creates an "auto" directory for both every distribution and for every module file. These are used by a couple of different auto-loading systems to store code fragments generated at install time, and various other modules written by the Perl "ancient masters". But the same mechanism is available to any dist or module to store any sort of data.
PackageNameperl-File-ShareDir
PackageRelease33.1
PackageVersion1.118
SHA-160C836CADA625728563A098446579C3DCFFCBCE3
SHA-256D3732E9FE45EB9777BCB60531998C27ED743281EE6E966D4DC638B8B8425B7A1
Key Value
MD56DE4876E9BB4D6078CD41EBEFEB98636
PackageArchnoarch
PackageDescriptionThe intent of File::ShareDir is to provide a companion to Class::Inspector and File::HomeDir, modules that take a process that is well-known by advanced Perl developers but gets a little tricky, and make it more available to the larger Perl community. Quite often you want or need your Perl module (CPAN or otherwise) to have access to a large amount of read-only data that is stored on the file-system at run-time. On a linux-like system, this would be in a place such as /usr/share, however Perl runs on a wide variety of different systems, and so the use of any one location is unreliable. Perl provides a little-known method for doing this, but almost nobody is aware that it exists. As a result, module authors often go through some very strange ways to make the data available to their code. The most common of these is to dump the data out to an enormous Perl data structure and save it into the module itself. The result are enormous multi-megabyte .pm files that chew up a lot of memory needlessly. Another method is to put the data "file" after the __DATA__ compiler tag and limit yourself to access as a filehandle. The problem to solve is really quite simple. 1. Write the data files to the system at install time. 2. Know where you put them at run-time. Perl's install system creates an "auto" directory for both every distribution and for every module file. These are used by a couple of different auto-loading systems to store code fragments generated at install time, and various other modules written by the Perl "ancient masters". But the same mechanism is available to any dist or module to store any sort of data.
PackageNameperl-File-ShareDir
PackageRelease33.1
PackageVersion1.118
SHA-178C1F00D07F8F0EB4B07D5B1DFC9C89F749F0C5D
SHA-2562EF8CC16A650A4128FB496629EB37C81E41C3A90DF993DC23F88068BC9DDAF46
Key Value
MD51C40995FCFF19C27CD3BC4D4F167A121
PackageArchnoarch
PackageDescriptionThe intent of File::ShareDir is to provide a companion to Class::Inspector and File::HomeDir, modules that take a process that is well-known by advanced Perl developers but gets a little tricky, and make it more available to the larger Perl community. Quite often you want or need your Perl module (CPAN or otherwise) to have access to a large amount of read-only data that is stored on the file-system at run-time. On a linux-like system, this would be in a place such as /usr/share, however Perl runs on a wide variety of different systems, and so the use of any one location is unreliable. Perl provides a little-known method for doing this, but almost nobody is aware that it exists. As a result, module authors often go through some very strange ways to make the data available to their code. The most common of these is to dump the data out to an enormous Perl data structure and save it into the module itself. The result are enormous multi-megabyte .pm files that chew up a lot of memory needlessly. Another method is to put the data "file" after the __DATA__ compiler tag and limit yourself to access as a filehandle. The problem to solve is really quite simple. 1. Write the data files to the system at install time. 2. Know where you put them at run-time. Perl's install system creates an "auto" directory for both every distribution and for every module file. These are used by a couple of different auto-loading systems to store code fragments generated at install time, and various other modules written by the Perl "ancient masters". But the same mechanism is available to any dist or module to store any sort of data.
PackageNameperl-File-ShareDir
PackageRelease3.2
PackageVersion1.118
SHA-185F33B2EDA9B8F177CB579C27048AE0B137B8E8F
SHA-25622DA3C82F5FEADD586CACC51F7CE846AB63940607F4CB22F795F831A73E9DA2F