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.
Changes from 0.3.3:
Mon Feb 2 22:34:28 EST 2004 Mark Rogaski
. Description: 0.3.6
Stripped line endings in common tests to allow tests to succeed
under non-UN*X environments. Also replaced an unnecessary handle
alias with the actual file name in t/file.t. Thanks to Jay Lawrence
and Terrence Brannon for pointing out the test problems.
Sat Sep 27 13:56:58 EDT 2003 Mark Rogaski
. Description: 0.3.5
Added a wrapper for &AutoLoader::AUTOLOAD to save the value
of $!, which is often clobbered before the substitution of
"%m" by logxxx().
Added a META.yml file and disabled autogeneration in Makefile.PL.
Sat Mar 8 11:43:41 EST 2003 Mark Rogaski
. Description: 0.3.4
Made the logxxx() calls transparent to all (current)
sprintf() formatting patterns. Not all formatting
errors will be caught before passed to sprintf(), but
the obviously malformed ones will be detected.
Added support for embedded newlines in messages passed to
logcarp() and logxcarp().
Package change: add HOMEPAGE.
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.
Log::Agent is a general logging framework aimed at reusable modules.
Instead of having modules insist on using their onw logging reporting
(by hardwiring calls to warn() or syslog()) which can conflict with
the final application's choice, one may use logwarn() for instance to
emit a warning.
