Result for 77827F8E3268B34AE64523C8006E980692FCC96E

Query result

Key Value
FileName./usr/share/man/man3/File::ShareDir.3pm.gz
FileSize4864
MD5B7B4528732BA02125D29F3BFE32F2CC6
SHA-177827F8E3268B34AE64523C8006E980692FCC96E
SHA-256E9ACE030987719D5871763AB873B01A0FDDF27C53018097303D74185AC2928E9
SSDEEP96:IiolSPm7K4AwA+8LR1sFc+EQONQzNpBQfWWd/ZLnkOw6Nynz1rPJAsKi:3olfWVOF9OqBpkhlZLRyh13
TLSHT198A18F578416AA10D51F5AFA432C9BE006855EC35E122AB36C0A946E8CCD3C4BD0DAFF
hashlookup:parent-total4
hashlookup:trust70

Network graph view

Parents (Total: 4)

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

Key Value
MD50189E708FF5D66BDA304BCB4EDB4B9B1
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.
PackageMaintainerhttps://bugs.opensuse.org
PackageNameperl-File-ShareDir
PackageRelease1.8
PackageVersion1.118
SHA-18FD38D3DED371A1DFE1806032D81221A5F957F80
SHA-25653F3EE501BBCEB1197343F74D63BB6B6073BC4DB34C13BDACFE5FD5F8C16A924
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
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
MD5C9CB170138D18E5F299369F13CB84E68
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.33
PackageVersion1.118
SHA-189160112C6F02720738B741654A7E492BA90ABD0
SHA-256C3F7C836981C145EF45C896326A0B15F9E5E7CC3705D7E2FF2E63317A2152B69