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.
1.22 Sep 30, 2005
- Added Exception::Class::Base->caught() so you can write
"My::Error->caught()". Apparently this is what Damian documented in
Perl Best Practices. Thanks to JD Hedden for pointing this out.
- Require Devel::StackTrace 1.12 to fix a test failure on Win32.
Reported by Garrett Goebel.
1.21 Apr 17, 2005
- Added Exception::Class->caught() as syntactic sugar for catching
exceptions in a "safe" manner. See the docs for details. Suggested
by Damian Conway.
does. This allows us to use dynamic PLISTs for Perl modules that are
built using Module::Build. Bump the PKGREVISION of p5-Module-Build
to 1.
* Drop the use of PERL5_USES_MODULE_BUILD and introduce a new variable
PERL5_MODULE_TYPE that is either "MakeMaker" or "Module::Build" that
names the framework used to build/install the module.
* Split out the variables set in perl5/buildlink3.mk that are also used
by perl5/module.mk into a new file perl5/vars.mk. Move some PERL5_*
variable definitions from pkgsrc/mk/bsd.pkg.use.mk into perl5/vars.mk.
This just centralizes the common PERL5_* definitions into a single
file location.
* Convert the known packages that use Module::Build to set
PERL5_MODULE_TYPE and PERL5_PACKLIST:
devel/p5-Class-Container
devel/p5-Exception-Class
devel/p5-Log-Dispatch
devel/p5-Array-Compare
textproc/p5-Pod-Coverage
www/p5-Apache-Session-Wrapper
www/p5-MasonX-Request-WithApacheSession
1.20 Jan 1, 2005
- Moved the Classes() method to Exception::Class, now as a function,
which is where it really belongs. Also corrected the docs for this
function, as they incorrectly implied that it would return all
subclasses, instead of just subclasses which were created when loading
Exception::Class.
- Added a Build.PL file, and releases are now signed with
Module::Signature.
- Added ignore_class and ignore_package constructor parameters. Patch
by Daisuke Maki.
module directory has changed (eg. "darwin-2level" vs.
"darwin-thread-multi-2level").
binary packages of perl modules need to be distinguishable between
being built against threaded perl and unthreaded perl, so bump the
PKGREVISION of all perl module packages and introduce
BUILDLINK_RECOMMENDED for perl as perl>=5.8.5nb5 so the correct
dependencies are registered and the binary packages are distinct.
addresses PR pkg/28619 from H. Todd Fujinaka.
Add DEPENDS on p5-Test-Simple, and update p5-Devel-StackTrace dependency.
Change log:
1.19 Mar 10, 2004
- Identical to 1.18 except that it requires Devel::StackTrace 1.10,
which fixes a failure in this package's test when run with Perl 5.6.1.
Reported by Jesse Erlbaum.
1.18 Feb 21, 2004
- Added RespectOverload class method, which can be used to control the
respect_overload parameter for Devel::StackTrace objects.
1.17 Feb 20, 2004
- Document that new() is always called to create an
Exception::Class::Base object. Suggested by Steve Hay.
- Fix a test that failed with Devel::StackTrace 1.05. Basically, the
test expected output from Devel::StackTrace that reflected a bug that
was fixed in 1.05. Reported by Jesse Vincent.
1.16 Sep 25, 2003
- David Wheeler's patch exposed a bug in Devel::StackTrace which could
cause exceptions to not have any value set for package, file, or line.
This is fixed by depending on Devel::StackTrace 1.04. This release is
otherwise identical to 1.15. Reported by Steve Hay.
1.15 Sep 17, 2003
- Exceptions thrown from an alias subroutine always had
"Exception::Class" as their package name. Patch by David Wheeler.
This module allows you to declare hierarchies of exception classes for
use in your code. It also provides a simple exception class that it
uses as the default base class for all other exceptions.
You may choose to use another base class for your exceptions.
Regardless, the ability to declare all your exceptions at compile time
is a fairly useful trick and helps push people towards more structured
use of exceptions.
