Parents (Total: 3)

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

Key	Value
MD5	0C8802CB8BB01DE73D635B04E2FF1311
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.
PackageMaintainer	umeabot <umeabot>
PackageName	perl-Test-Perl-Critic-Progressive
PackageRelease	8.mga7
PackageVersion	0.30.0
SHA-1	74BF21BCE76FC17CE5B1C1698685678291C6CF16
SHA-256	4162BB0DADDF06E6CBFC9931E1691EE2C37115B57EDE52DF1A645D731052EA24

Key	Value
MD5	8C28FEECC62F2E4DEC173006741B1177
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.
PackageMaintainer	umeabot <umeabot>
PackageName	perl-Test-Perl-Critic-Progressive
PackageRelease	9.mga8
PackageVersion	0.30.0
SHA-1	0EC3FB6C142DDD5D498230244FAA928970806833
SHA-256	8F5B0259101B24D13209C24325A5213A7FF85660A500B858BB72D6BA07DAC873

Key	Value
MD5	1DF6865D48850DD874A70CD29A6F7E4D
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.
PackageMaintainer	umeabot <umeabot>
PackageName	perl-Test-Perl-Critic-Progressive
PackageRelease	10.mga9
PackageVersion	0.30.0
SHA-1	1C6990E8443C36237773CAD15299B02124A48292
SHA-256	445FB404E5A835B4D0A9FF59BDEA994C7FBEE3400B8753EC4A5DC079079A291F