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=...").
Version 6.00 17.02.2008
+ Oops. Fixed version number. '5.10' is less than '5.9'. I thought
CPAN would handle this but apparently not..
Version 5.10 10.01.2008
+ Removed the circular dependency on Object::Deadly. It was only
used for testing and would only succeed if you already had O::D
installed.
Version 5.8 09.10.2006
+ Stop testing that ->VERSION is a specific thing. I'm not sure why
that was ever tested in the first place.
Version 5.7 02.10.2006
+ Stop PAUSE from attempting to index DB package.
Version 5.6 02.10.2006
+ Fixed test to predefined croak/confess/cluck/carp functions don't
break tests.
+ Use Object::Deadly even saner.
+ Use named lexicals in diag().
+ Skip testing import of carp/croak/cluck/confess if they existed
prior to loading Carp::Clan.
+ Use exists &foo/defined &foo instead of symbol table hackery.
+ Remove all the symbol table hackery that had notes about avoiding
symrefs. That's dumb. It's better to be clear and have symrefs
than have unreadble code w/o symrefs.
+ Remove gratituous & sigil on function calls.
+ Changed f() so it accepts 1st parameter of carp/cluck/confess/croak
instead of 1/2/3/4.
+ Renamed files.
Version 5.5 02.10.2006
+ Change 01_..._carp.t to use Object::Deadly only if it is 0.08+
+ Changed wording of the O::D request in Makefile.PL
+ Allowed everything to be perltidied.
This module reports errors from the perspective of the caller of a
"clan" of modules, similar to "Carp.pm" itself. But instead of giving it
a number of levels to skip on the calling stack, you give it a pattern
to characterize the package names of the "clan" of modules which shall
never be blamed for any error. :-)
So these modules stick together like a "clan" and any error which occurs
will be blamed on the "outsider" script or modules not belonging to this
"clan".
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.
