Parents (Total: 5)

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

Key	Value
MD5	06D9CE60B77F9055AC356D7B99A215BD
PackageArch	noarch
PackageDescription	Applying coding standards to large amounts of legacy code is a daunting task. Often times, legacy code is so non-compliant that it seems downright impossible. But, if you consistently chip away at the problem, you will eventually succeed! Test::Perl::Critic::Progressive uses the the Perl::Critic manpage engine to prevent further deterioration of your code and *gradually* steer it towards conforming with your chosen coding standards. The most effective way to use Test::Perl::Critic::Progressive is as a unit test that is run under a continuous-integration system like CruiseControl or AntHill. Each time a developer commits changes to the code, this test will fail and the build will break unless it has the same (or fewer) Perl::Critic violations than the last successful test. See the the "NOTES" manpage for more details about how this test works.
PackageName	perl-Test-Perl-Critic-Progressive
PackageRelease	lp150.4.2
PackageVersion	0.03
SHA-1	42F3663750573C6C2203D56D7B4850651F8A5B84
SHA-256	A64827778C62E1767576C47D351920EA9929BAA0EBEB3BB432B051DF83F38645

Key	Value
MD5	5872C330B8FA54FFFC8FBE864B105885
PackageArch	noarch
PackageDescription	Applying coding standards to large amounts of legacy code is a daunting task. Often times, legacy code is so non-compliant that it seems downright impossible. But, if you consistently chip away at the problem, you will eventually succeed! Test::Perl::Critic::Progressive uses the the Perl::Critic manpage engine to prevent further deterioration of your code and *gradually* steer it towards conforming with your chosen coding standards. The most effective way to use Test::Perl::Critic::Progressive is as a unit test that is run under a continuous-integration system like CruiseControl or AntHill. Each time a developer commits changes to the code, this test will fail and the build will break unless it has the same (or fewer) Perl::Critic violations than the last successful test. See the the "NOTES" manpage for more details about how this test works.
PackageName	perl-Test-Perl-Critic-Progressive
PackageRelease	lp152.4.1
PackageVersion	0.03
SHA-1	8AF10D0151EECD8B862C797EC61E89C586CEF681
SHA-256	EBEA18A7CF293B9FF23391B813479D395FDE542CDEDEDEDEC60E04C0DFE07D2B

Key	Value
MD5	2847B3748E954CA26ECE6835A8F9A156
PackageArch	noarch
PackageDescription	Applying coding standards to large amounts of legacy code is a daunting task. Often times, legacy code is so non-compliant that it seems downright impossible. But, if you consistently chip away at the problem, you will eventually succeed! Test::Perl::Critic::Progressive uses the the Perl::Critic manpage engine to prevent further deterioration of your code and *gradually* steer it towards conforming with your chosen coding standards. The most effective way to use Test::Perl::Critic::Progressive is as a unit test that is run under a continuous-integration system like CruiseControl or AntHill. Each time a developer commits changes to the code, this test will fail and the build will break unless it has the same (or fewer) Perl::Critic violations than the last successful test. See the the "NOTES" manpage for more details about how this test works.
PackageName	perl-Test-Perl-Critic-Progressive
PackageRelease	4.1
PackageVersion	0.03
SHA-1	45CA031DD0782ED47836E56972D89ADA93628239
SHA-256	8E32C3C6F8F216FDE43F124136BB8546E6EE9732AF5ACD082ADF058BD3D981D7

Key	Value
MD5	791752C250FB0A81FBF801AA5171A3B7
PackageArch	noarch
PackageDescription	Applying coding standards to large amounts of legacy code is a daunting task. Often times, legacy code is so non-compliant that it seems downright impossible. But, if you consistently chip away at the problem, you will eventually succeed! Test::Perl::Critic::Progressive uses the the Perl::Critic manpage engine to prevent further deterioration of your code and *gradually* steer it towards conforming with your chosen coding standards. The most effective way to use Test::Perl::Critic::Progressive is as a unit test that is run under a continuous-integration system like CruiseControl or AntHill. Each time a developer commits changes to the code, this test will fail and the build will break unless it has the same (or fewer) Perl::Critic violations than the last successful test. See the the "NOTES" manpage for more details about how this test works.
PackageName	perl-Test-Perl-Critic-Progressive
PackageRelease	lp153.4.1
PackageVersion	0.03
SHA-1	8BB53D6ECE862C6788C123308AEAB51F66D5D1CE
SHA-256	DE494DBAA98F7909CBC521F1DB9B6E1189EC300950F1AD3B9B40A5D5EAD5225E

Key	Value
MD5	2DB7AEB8A772672601F4DA5B8ACE1098
PackageArch	noarch
PackageDescription	Applying coding standards to large amounts of legacy code is a daunting task. Often times, legacy code is so non-compliant that it seems downright impossible. But, if you consistently chip away at the problem, you will eventually succeed! Test::Perl::Critic::Progressive uses the the Perl::Critic manpage engine to prevent further deterioration of your code and *gradually* steer it towards conforming with your chosen coding standards. The most effective way to use Test::Perl::Critic::Progressive is as a unit test that is run under a continuous-integration system like CruiseControl or AntHill. Each time a developer commits changes to the code, this test will fail and the build will break unless it has the same (or fewer) Perl::Critic violations than the last successful test. See the the "NOTES" manpage for more details about how this test works.
PackageName	perl-Test-Perl-Critic-Progressive
PackageRelease	lp151.4.1
PackageVersion	0.03
SHA-1	1EC0E5897F2149E3F28001B09C7BE89DC22DF7AD
SHA-256	04CF78B21B7B1E724496D15992D64F3B8E00F41AF29D5B963819FA484957A45A