2012-10-31 12:19:55 by Aleksej Saushev | Files touched by this commit (1460) |
Log message:
Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.
|
2012-10-03 23:59:10 by Thomas Klausner | Files touched by this commit (2798) |
Log message:
Bump all packages that use perl, or depend on a p5-* package, or
are called p5-*.
I hope that's all of them.
|
2011-08-14 14:26:51 by OBATA Akio | Files touched by this commit (406) |
Log message:
Revision bump after updating perl5 to 5.14.1.
|
2010-08-21 18:37:14 by Stoned Elipot | Files touched by this commit (1724) | |
Log message:
Bump the PKGREVISION for all packages which depend directly on perl,
to trigger/signal a rebuild for the transition 5.10.1 -> 5.12.1.
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=..."), minus the packages updated after
the perl package update.
sno@ was right after all, obache@ kindly asked and he@ led the
way. Thanks!
|
2009-06-13 08:46:48 by Roland Illig | Files touched by this commit (67) |
Log message:
Ran pkglint --autofix on the devel/ category. Most of the changes are
simple white-space issues like indentation and trailing spaces. The
others are cross-references for Makefile.common.
|
2008-10-19 21:19:25 by Havard Eidnes | Files touched by this commit (1179) |
Log message:
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-06-23 05:59:19 by David Brownlee | Files touched by this commit (3) | |
Log message:
Import p5-Test-use-ok-0.02
According to the Test::More documentation, it is recommended to run
use_ok() inside a BEGIN block, so functions are exported at
compile-time and prototypes are properly honored.
That is, instead of writing this:
use_ok( 'Some::Module' );
use_ok( 'Other::Module' );
One should write this:
BEGIN { use_ok( 'Some::Module' ); }
BEGIN { use_ok( 'Other::Module' ); }
However, people often either forget to add BEGIN, or mistakenly group
use_ok with other tests in a single BEGIN block, which can create subtle
differences in execution order.
With this module, simply change all use_ok in test scripts to use ok,
and they will be executed at BEGIN time. The explicit space after use
makes it clear that this is a single compile-time action.
|