Commit graph

6 commits

Author SHA1 Message Date
he
b021813da0 Bump the PKGREVISION for all packages which depend directly on perl,
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=...").
2008-10-19 19:17:40 +00:00
rhaen
09548adc29 - updated package to 0.084
- 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.
2007-12-11 11:58:04 +00:00
jlam
56ba4d2690 Remove empty PLISTs from pkgsrc since revision 1.33 of plist/plist.mk
can handle packages having no PLIST files.
2007-10-25 16:54:26 +00:00
jlam
9c8b5ede43 Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where no
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.
2006-03-04 21:28:51 +00:00
wiz
9d953594c3 Grammar fix, from Leonard Schmidt in private mail. 2005-11-24 18:50:40 +00:00
wiz
ec69205bc1 Initial import of p5-Test-NoWarnings:
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.
2005-11-23 22:00:02 +00:00