Age | Commit message (Collapse) | Author | Files | Lines |
|
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.
|
|
Revision history for Perl extension Catalyst::Plugin::StackTrace
0.12 2012-07-12 15:13:00 BST
- Convert from Class::Accessor::Fast to Moose (dakkar)
|
|
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.
|
|
|
|
are called p5-*.
I hope that's all of them.
|
|
URL should be as HOMEPAGE in the Makefile.
|
|
|
|
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 license definition
Upstream changes:
0.11 2009-10-18 18:30:00 BST
- Fixup copyright info
|
|
devel/p5-Class-MOP. A late detected incompible change forced it.
|
|
- Updating package for p5 module Catalyst::Plugin::StackTrace from 0.09
to 0.10
- Setting license to gnu-gpl-v2
- Adjusting dependencies
Upstream changes:
0.10 2009-04-20 13:50:00
- Switch to MRO::Compat
|
|
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=...").
|
|
Pkgsrc changes:
o Adjust dependencies
Upstream changes:
0.09 2008-09-03 12:00:00
- Filter out unwanted stack frames and attributes in the
$SIG{__DIE__} handler instead of finalize_error().
- Avoid stringifying refs in the trace, since we now throw them
away immediately.
|
|
This plugin will enhance the standard Catalyst debug screen by including
a stack trace of your appliation up to the point where the error
occurred. Each stack frame is displayed along with the package name,
line number, file name, and code context surrounding the line number.
WWW: http://search.cpan.org/dist/Catalyst-Plugin-StackTrace/
|