ChangeLog:
At the request Michael Schwern, do not "require threads" any longer as
it can upset Test::Builder. Anyone using threads should already have
done that themselves. Anyway not, doesn't need it.
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!
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=...").
0.107
Test::Tester::Capgture::new used to just return __PACKAGE__
because Test::Builder::new enforced it's singleton nature by
return __PACKAGE__. That has since changed, Test::Builder::new now
returns a blessed has and around version 0.78, Test::Builder::todo
started wanting to modify $self. To cope with this, we now return
a blessed hash. This is a short-term hack, the correct thing to do
is to detect which style of Test::Builder we're dealing with and
act appropriately.
- USER_DESTDIR support added
- new maintainer for the package
- ok'ed by rillig
Changelog:
0.106
Some doc clarifications and improvements.
0.105
Fixed documentation for run_tests - looks like I copied code for
check_test and didn't alter it correctly. Ricardo Signes pointed out
the errors.
Removed the code and docs related to the $name parameter of run_tests,
it had no effect and a name makes no sense (again a hang over from
factoring this out of check_tests I guess).
0.104
Removed a bogus entry for Exporter in @ISA in Test::Tester::Capture
and add a "use Test::Builder". This can cause problems that I can't
reproduce. Thanks to Andres Koenig.
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.
