pkgsrc changes:
- Adding license definition
Upstream changes:
1.01 15 Jan 2010 - Adam Kennedy
- My release automation accidentally decided that Test::NoWarnings
was a Perl licensed distribution. Added in the appropriate changes
to make sure it is correctly built with the LGPL license.
1.00 11 Jan 2010 - Adam Kennedy
- Cleaned and updated the packaging of the module, the dependencies
and the Makefile.PL contents, but otherwise remains unchanged (ADAMK)
- Now makes explicit the Perl 5.006 dependency that was previously
an undocumented implicit dependency (ADAMK)
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=...").
- USER_DESTDIR support added
- new maintainer for the package
- ok'ed by rillig
Changelog:
0.084
Perl 5.005 throws a warning when accessing $Carp::VERSION and was
causing a test to fail.
0.083
Finally got rid of INSTALLDIRS => 'perl' from Makefile.PL. It should
never have been there but removing it could cause hassle because of
Perl's weird ordering of include directories. Basically if an older
version exists in the 'perl' installdir it could be picked up instead
of the newer version.
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.
In general, your tests shouldn't produce warnings. This modules
causes any warnings to be captured and stored. It automatically
adds an extra test that will run when your script ends to check
that there were no warnings. If there were any warnings, the test
will give a "not ok" and diagnostics of where, when, and what the
warning was, including a stack trace of what was going on when it
occurred.
If some of your tests are supposed to produce warnings then you
should be capturing and checking them with Test::Warn, that way
Test::NoWarnings will not see them and so not complain.
