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!
1.92)
Pkgsrc changes:
- Be conservative set the package version to 1.9.2
- Use the "dist/" variant for HOMEPAGE
Upstream changes:
1.91 Wed 14 Jul 2010 01:07:05 BST
- Incorporate patches from Florian Ragwitz and Yuval Kogman
(see http://github.com/robinhouston/PadWalker/commits/master)
1.92 Thu 15 Jul 2010 17:05:05 BST
- Remove "Jobsian dot file cruft" reported by Steve Mynott.
- Incorporate patch from Fuji, Goro, correcting earlier patch from Yuval Kogman.
license to the value from META.yml.
Upstream changes:
1.8 Thu 25 Jun 2009 21:17:17 BST
- Apply patches from doy (#41710) and nothingmuch (set_closed_over).
1.9 Fri 26 Jun 2009 10:01:17 BST
- Identical to 1.8, but with the bogus metadata ._ files removed
from the distributed tar file.
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=...").
PadWalker is a module which allows you to inspect (and even change!)
lexical variables in any subroutine which called you. It will only
show those variables which are in scope at the point of the call.
PadWalker is particularly useful for debugging. It's even used by
Perl's built-in debugger. (It can also be used for evil, of course.)
I wouldn't recommend using PadWalker directly in production code,
but it's your call. Some of the modules that use PadWalker internally
are certainly safe for and useful in production.
