Parents (Total: 14)

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

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	6DE4876E9BB4D6078CD41EBEFEB98636
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.1
PackageVersion	1.118
SHA-1	78C1F00D07F8F0EB4B07D5B1DFC9C89F749F0C5D
SHA-256	2EF8CC16A650A4128FB496629EB37C81E41C3A90DF993DC23F88068BC9DDAF46

Key	Value
MD5	1C40995FCFF19C27CD3BC4D4F167A121
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	3.2
PackageVersion	1.118
SHA-1	85F33B2EDA9B8F177CB579C27048AE0B137B8E8F
SHA-256	22DA3C82F5FEADD586CACC51F7CE846AB63940607F4CB22F795F831A73E9DA2F

Key	Value
MD5	C240F70D5F95C0F301BED394B22B572B
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.1
PackageVersion	1.118
SHA-1	60C836CADA625728563A098446579C3DCFFCBCE3
SHA-256	D3732E9FE45EB9777BCB60531998C27ED743281EE6E966D4DC638B8B8425B7A1

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	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	0189E708FF5D66BDA304BCB4EDB4B9B1
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	1.8
PackageVersion	1.118
SHA-1	8FD38D3DED371A1DFE1806032D81221A5F957F80
SHA-256	53F3EE501BBCEB1197343F74D63BB6B6073BC4DB34C13BDACFE5FD5F8C16A924

Key	Value
MD5	B69FA50A7825656BF0FBB3D61EDD8449
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	lp151.33.1
PackageVersion	1.118
SHA-1	F886331B29355ED35A03298AE9CEFFDB50D7BC45
SHA-256	33905F56CEBCFC6E561D76B0F083FD619BC0909EE772522613D1C4D16C437B15

Key	Value
MD5	C9CB170138D18E5F299369F13CB84E68
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.33
PackageVersion	1.118
SHA-1	89160112C6F02720738B741654A7E492BA90ABD0
SHA-256	C3F7C836981C145EF45C896326A0B15F9E5E7CC3705D7E2FF2E63317A2152B69

Key	Value
MD5	E04E1AD71E8CAC720CF1E816BFD5E1E2
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	lp152.33.1
PackageVersion	1.118
SHA-1	D8FE0A233BDF196B2E7176A37CC05E06E39D104E
SHA-256	C5FE97DFE5E1D4F1AAC3E39DA3FF8E45547A1CD6C4630DD67EFA63B4851F9BB2

Key	Value
MD5	3B881C3193DF170FF38B792ADB22BC16
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	3.1
PackageVersion	1.118
SHA-1	569C88CEF815A93268BC7477DE9E006B3AFE0EC9
SHA-256	8D754C624EF74C13E08AFE7CF9B6F1AC9E49FAAA0170FC5A0CE4671297BE4941

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

Key	Value
MD5	40E11260D1D4361081C7F400AA3369F0
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.1
PackageVersion	1.118
SHA-1	4D9780830D0CE604C0C1DD56A1B5BE07A91B3163
SHA-256	248D52E502AA1A28A7908433C7BE8886E0D71204DD5E0E5395B7395B4DF4F90B

Key	Value
MD5	EDEA13D665996AC4C1F15F6EAE5C65C2
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.1
PackageVersion	1.118
SHA-1	E5A983AFDD109EAAFAB46B4829B9ECAE6CA63BD4
SHA-256	A6E1E657CCB3A1F18C9A222957D086A17ADE915980670212B1113C5EC0422DB2