Parents (Total: 7)

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

Key	Value
MD5	6F22A24943386B082F002508A314C10A
PackageArch	noarch
PackageDescription	The 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.
PackageMaintainer	CloudLinux Packaging Team <packager@cloudlinux.com>
PackageName	perl-File-ShareDir
PackageRelease	3.el8
PackageVersion	1.104
SHA-1	39647A1E83878012D574325AF26E59AF9AA092C0
SHA-256	666C850AFB7441CD3D02DA3F6754324E8600A276A6412F5A8D1656BEAB858C7F

Key	Value
FileName	perl-File-ShareDir-1.104-1.22.noarch.rpm
FileSize	27600
MD5	F77A74E3F02174D07085418417652FF3
PackageArch	noarch
PackageDescription	The 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.
PackageMaintainer	https://www.suse.com/
PackageName	perl-File-ShareDir
PackageRelease	1.22
PackageVersion	1.104
RDS:package_id	263809
SHA-1	3316CF94B1CB7188858A665FDE1D05B995DD26F5
SHA-256	235166EAD1B85251C586BF94F3FBACF55A7CE686263335A4E3BC3000D27C2F84
insert-timestamp	1654958808.3516319
source	modern.db

Key	Value
MD5	33EA994244FBD05B589F0B5E7291F632
PackageArch	noarch
PackageDescription	The 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.
PackageMaintainer	https://bugs.opensuse.org
PackageName	perl-File-ShareDir
PackageRelease	lp150.1.7
PackageVersion	1.104
SHA-1	32CE6307D1D6A10F9853A5767A67900455A9F304
SHA-256	DBCDEC69C9EAD477A3A0F76924680D977E0ED69289589103742228220DC50FA7

Key	Value
MD5	550E888BE62A7D84922D3D960C87B753
PackageArch	noarch
PackageDescription	The 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.
PackageMaintainer	CBS <cbs@centos.org>
PackageName	rh-perl526-perl-File-ShareDir
PackageRelease	3.el7
PackageVersion	1.104
SHA-1	F58CB88341527EBBBD0F1BE072D605F27CCD3CE5
SHA-256	B2D87F187FB708D98FB3AAC771E26FF5451D5E4D16E60BD447F0951AEAE42FC3

Key	Value
MD5	BD1938FD5AB02796169F1C2D7E081F2E
PackageArch	noarch
PackageDescription	The 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.
PackageMaintainer	https://bugs.opensuse.org
PackageName	perl-File-ShareDir
PackageRelease	lp151.2.1
PackageVersion	1.104
SHA-1	BBB77EF2695DDA2960751AF32BCD7DE4EA9A2F37
SHA-256	5889686CC8365588885B02A42F7F82673FD39B901F73FDB9E16B5496C9FA2943

Key	Value
MD5	BDD8B64C54447658DA10E1C1129DCBAD
PackageArch	noarch
PackageDescription	The 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.
PackageMaintainer	https://bugs.opensuse.org
PackageName	perl-File-ShareDir
PackageRelease	lp152.3.2
PackageVersion	1.104
SHA-1	1422DEF4EC2BEBBFDDE8D186E1C85DC5F48BCE34
SHA-256	29C5D81C19CA28EC55063986C70780368840E0EC156EBE309B7A785D4E089223

Key	Value
MD5	AA5CD0AA71F85C5B32F3099002E12D8E
PackageArch	noarch
PackageDescription	The 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.
PackageMaintainer	CentOS Buildsys <bugs@centos.org>
PackageName	perl-File-ShareDir
PackageRelease	3.el8
PackageVersion	1.104
SHA-1	E5CFCA9AF508D04A5B527375EB38DA57915BFC10
SHA-256	3CFBAF649E0E29098610D07A12148A7F699EA64EF83CD524902C3EB8F74733AD