6 Commits (de6564e6c90ea58f68a5d920d04d91dcb4471bd4)

Author	SHA1	Message	Date
Paul Howarth	de6564e6c9	Update to 0.19 ... - New upstream release 0.19: - Test::CPAN::Changes now accepts version entries ending in '-TRIAL' (CPAN RT#76882) - releases() in CPAN::Changes also accepts entries ending in '-TRIAL' - Don't need to remove empty directories from buildroot - Drop %defattr, redundant since rpm 4.4	13 years ago
Paul Howarth	9d4643f8ee	Fedora 17 mass rebuild	13 years ago
Paul Howarth	463fa84012	Update to 0.18 ... - New upstream release 0.18: - Expand changes_file_ok() to accept arguments so that a specific version may be checked - Add $VERSION to Test::CPAN::Changes so it plays nice with the toolchain e.g. Module::Install::AuthorRequires	13 years ago
Marcela Mašláňová	2ff42b22ab	Perl mass rebuild	14 years ago
Paul Howarth	1fc42896f2	Update to 0.17: ... - New upstream release 0.17: - Eliminate extra whitespace when release data is not defined (CPAN RT#67441) - Require version.pm 0.79, which introduced the $LAX regexp (CPAN RT#67613) - Add the option to sort groups	14 years ago
Paul Howarth	a147f6e889	Initial import of perl-CPAN-Changes-0.16-1 ... It is standard practice to include a Changes file in your distribution. The purpose of the Changes file is to help a user figure out what has changed since the last release. People have devised many ways to write the Changes file. A preliminary specification has been created (CPAN::Changes::Spec) to encourage module authors to write clear and concise Changes. This module will help users programmatically read and write Changes files that conform to the specification.	14 years ago