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!
pkgsrc changes:
- Adjusting dependencies
Upstream changes:
0.05 Sun, 29 Nov 2009 17:38:51 +0100
* Depend on a later version of PadWalker to avoid segfaults in the
Catalyst test suite.
pkgsrc changes:
- Adjusting dependencies
Upstream changes:
0.04 Sat, 12 Sep 2009 06:13:20 +0900
* Depend on PadWalker (Closes RT#49551).
0.03 Sat, 05 Sep 2009 09:42:43 +0200
* Port to Devel::Cycle. We're now able to report a broader range of leaks.
support Catalyst Developers using pkgsrc a bit better.
It's easy to create memory leaks in Catalyst applications and often they're
hard to find. This module tries to help you finding them by automatically
checking for common causes of leaks.
Right now, only one cause for leaks is looked for: putting a closure, that
closes over the Catalyst context (often called $ctx or $c), onto the stash,
without weakening the reference first. More checks might be implemented in
the future.
This module is intended for debugging only. I suggest to not enable it in a
production environment.