Parents (Total: 29)

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

Key	Value
MD5	9F6916AEE96E99C7D46A56A0D13DF846
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.
PackageName	perl-File-ShareDir
PackageRelease	lp153.33.12
PackageVersion	1.118
SHA-1	02E9ECA84EA8DE5D3D7C1A6B8CACD5019ED0213C
SHA-256	B29F41CAA5BB10C68759C51AA44F55D17658F636BBC88174474DFA147DFE999D

Key	Value
MD5	9FE1765E4950B321DC933B53DCBAFC44
PackageArch	noarch
PackageDescription	Locate per-dist and per-module shared files
PackageMaintainer	umeabot <umeabot>
PackageName	perl-File-ShareDir
PackageRelease	2.mga7
PackageVersion	1.116.0
SHA-1	034CC7EC8AA8B70E13EC1CEB5F91B2347B98A571
SHA-256	249D0BD810F43FEB7EFD8689229985DCF95E81DF9B50CAD8881C3B61DD3B4494

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	D435B0E64EB2961B7BA5D133E55A9218
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.
PackageName	perl-File-ShareDir
PackageRelease	lp150.33.1
PackageVersion	1.118
SHA-1	16E1F45793DCF02B84B56D19E12AAE9EABEC3853
SHA-256	66AFBBC72A8A19E45D30353DE7868D14D428A08473A9872E9F5A68C0E1FF3915

Key	Value
MD5	91D5039738B75C25A9AC62F09E6FC63D
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.
PackageName	perl-File-ShareDir
PackageRelease	1.3
PackageVersion	1.118
SHA-1	2FCA69E7C6F3C9273001550022CCAC855EAD6616
SHA-256	D8499FE5CD64B286D23006B5353882E49EADC0467D2E8389D91AC6534FF58ACA

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
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	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
MD5	0254F9B04F1A8E4DB065698F892EF04D
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	Fedora Project
PackageName	perl-File-ShareDir
PackageRelease	2.fc34
PackageVersion	1.118
SHA-1	40021CCAAB4CF4B704AD4F67390CAA4CB8386752
SHA-256	696CAAAEF429D308D8FDE2CBDBF6656B1072EAFC3D3699196C90F59617DA464F

Key	Value
MD5	62847331D48D2AFD9D99781CAB22FA3F
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.
PackageName	perl-File-ShareDir
PackageRelease	33.2
PackageVersion	1.118
SHA-1	4D00EFDEB5B2E343308ED01E2F0E46B9BA79F470
SHA-256	3FE1441B8140B1826AAB615815F0F9B80A33A7D0948AD761999E026B86CB9E4F