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!
Pkgsrc changes:
- adjust dependencies
- Set PERL5_MODULE_TYPE to Module::Install::Bundled
Upstream changes:
0.13 Fri, 07 May 2010 22:49:46 +0200
* Stop shipping some author tests, so users stupid enough to run them won't
spam me with fail reports.
- Updating package of p5 module Class::C3::Adopt::Next from 0.11 to 0.12
- Apply Module::Install switch to skip dependency check, but keep
bundled Module::Install (extended)
- Adjusting license according to META.yaml
Upstream changes:
0.12 Mon, 08 Jun 2009 14:16:34 +0200
* Update copyright notice.
* A couple of pod whitespace changes.
- Updating package for p5 module Class::C3::Adopt::NEXT from 0.10 to 0.11
upstream changes:
0.11 Tue, 19 May 2009 18:34:17 +0100
* Change wording of warning to be more clear.
- Updating package for p5 module Class::C3::Adopt::NEXT from 0.09 to 0.10
Upstream changes:
0.10 Tue, 12 May 2009 13:23:52 +0200
* Depend on Test::Exception 0.27 to avoid breaking tests on older versions
(Closes: RT#45986).
required dependency for the update of Catalyst::Runtime
(/www/p5-Catalyst-Runtime) to 5.800.
This module is intended as a drop-in replacement for NEXT, supporting the same
interface, but using Class::C3 to do the hard work. You can then write new
code without NEXT, and migrate individual source files to use Class::C3 or
method modifiers as appropriate.
