a) refer 'perl' in their Makefile, or
b) have a directory name of p5-*, or
c) have any dependency on any p5-* package
Like last time, where this caused no complaints.
COMMENT should not be longer than 70 characters.
COMMENT should not begin with 'A'.
COMMENT should not begin with 'An'.
COMMENT should not begin with 'a'.
COMMENT should not end with a period.
COMMENT should start with a capital letter.
pkglint warnings. Some files also got minor formatting, spelling, and style
corrections.
Changes from previous:
----------------------
1.19 Mon 10 May 2010 - Adam Kennedy
- Adding abstracts to ::API and ::FAQ
- Update Module::Install to 1.00
pkgsrc changes:
- adjust dependencies (partial reordered)
Upstream changes:
1.18 Mon 10 May 2010 - Adam Kennedy
- POD typo fix to keep the Debian nazis happy :)
1.17 Mon 10 May 2010
- Updating to Module::Install 0.95
- Bundling newer author tests
- Removing a three-argument open that some overzealous external
contributor added.
- Added support for the .tgz extension, behaving the same as .tar.gz
- Added support for github tarball URLs in the format
http://github.com/gitpan/Config-Tiny/tarball/2.12
to trigger/signal a rebuild for the transition 5.10.1 -> 5.12.1.
The list of packages is computed by finding all packages which end
up having either of PERL5_USE_PACKLIST, BUILDLINK_API_DEPENDS.perl,
or PERL5_PACKLIST defined in their make setup (tested via
"make show-vars VARNAMES=..."), minus the packages updated after
the perl package update.
sno@ was right after all, obache@ kindly asked and he@ led the
way. Thanks!
Development and Refactoring Environment.
The pip ("Perl Installation Program") console application is used to install
Perl distributions in a wide variety of formats, both from CPAN and from
external third-party locations, while supporting module dependencies that go
across the boundary from third-party to CPAN.
Using pip you can install CPAN modules, arbitrary tarballs from both the
local file-system or across the internet from arbitrary URIs.
