Result for 6FDDE24C8E528B7D3C4963BD6D24F79D1E848622

Query result

Key Value
FileName./usr/share/man/man3/File::ShareDir.3pm.gz
FileSize3577
MD58E2AB631DA9C05B005A558DE68F7A439
RDS:package_id263811
SHA-16FDDE24C8E528B7D3C4963BD6D24F79D1E848622
SHA-256E6A7BB87FC7EDA357FB3C5192F444DA1E824924E3281FC452E10F1F96653D65A
SSDEEP96:/P/gyKIvbp/MesxZZCl6lGKoptEz3f6Xx/UwUBFBtEyQAV:/nRN/xsrZClAGKGksJfUBFLJ
TLSHT180717D78BDA5C68AE8C7B47FDD618819B0A077401AA008C7055FFEFA330A6A3F54890D
insert-timestamp1654960138.299875
sourcemodern.db
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
MD5BDD8B64C54447658DA10E1C1129DCBAD
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
PackageReleaselp152.3.2
PackageVersion1.104
SHA-11422DEF4EC2BEBBFDDE8D186E1C85DC5F48BCE34
SHA-25629C5D81C19CA28EC55063986C70780368840E0EC156EBE309B7A785D4E089223
Key Value
FileNameperl-File-ShareDir-1.104-1.22.noarch.rpm
FileSize27600
MD5F77A74E3F02174D07085418417652FF3
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://www.suse.com/
PackageNameperl-File-ShareDir
PackageRelease1.22
PackageVersion1.104
RDS:package_id263809
SHA-13316CF94B1CB7188858A665FDE1D05B995DD26F5
SHA-256235166EAD1B85251C586BF94F3FBACF55A7CE686263335A4E3BC3000D27C2F84
insert-timestamp1654958808.3516319
sourcemodern.db
Key Value
MD5BD1938FD5AB02796169F1C2D7E081F2E
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
PackageReleaselp151.2.1
PackageVersion1.104
SHA-1BBB77EF2695DDA2960751AF32BCD7DE4EA9A2F37
SHA-2565889686CC8365588885B02A42F7F82673FD39B901F73FDB9E16B5496C9FA2943
Key Value
MD533EA994244FBD05B589F0B5E7291F632
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
PackageReleaselp150.1.7
PackageVersion1.104
SHA-132CE6307D1D6A10F9853A5767A67900455A9F304
SHA-256DBCDEC69C9EAD477A3A0F76924680D977E0ED69289589103742228220DC50FA7