pkgsrc changes:
- Adding license definition
Upstream changes:
Version 6.04 24.10.2009
+ Solved RT ticket #50796 (inform type of license)
+ Made the test suite compatible with Perl versions < v5.6.0
Upstream changes:
Version 6.03 18.10.2009
+ Re-release to resolve confusion in CPAN caused by intermediate release
of Carp::Clan 5.4 (backport of bugfix #50560 below for Perls < v5.6.0)
Version 6.02 17.10.2009
+ Forgot to fix the bug of duplicated prefixes in _longmsg as well
Version 6.01 16.10.2009
+ Fixed bug of duplicated prefixes (RT ticket #50560)
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".
