Do it for all packages that
* mention perl, or
* have a directory name starting with p5-*, or
* depend on a package starting with p5-
like last time, for 5.18, where this didn't lead to complaints.
Let me know if you have any this time.
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.
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!
- Updating package for p5 module Test::ClassAPI from 1.05nb1 to 1.06
- Adjusting dependencies, LICENSE and PERL5_MODULE_TYPE
Upstream changes:
1.06 Mon 13 Jul 2009
- No functional changes
- Updating to Module::Install::DSL 0.91
- Updating to new author tests
- Updating minimum Perl version to 5.6
to trigger/signal a rebuild for the transition 5.8.8 -> 5.10.0.
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=...").
1.03 Thu 15 Feb 2007
- Moving from old CVS to new SVN repository
- Cleaning up unit tests
- Updating some too-old dependencies
- Upgrading Makefile.PL to use Module::Install 0.64
developer is officially maintaining the package.
The rationale for changing this from "tech-pkg" to "pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list). Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.
For many APIs with large numbers of classes, it can be very useful
to be able to do a quick once-over to make sure that classes,
methods, and inheritance is correct, before doing more comprehensive
testing. This module aims to provide such a capability.
