pkgsrc - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
2008-10-19	Bump the PKGREVISION for all packages which depend directly on perl,	he	1	-1/+2
	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-05-28	Updated devel/Test-Tester to 0.107	abs	2	-7/+9
	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.
2007-12-11	- updated package to 0.106	rhaen	2	-8/+8
	- 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.
2007-10-25	Remove empty PLISTs from pkgsrc since revision 1.33 of plist/plist.mk	jlam	1	-1/+0
	can handle packages having no PLIST files.
2006-03-04	Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where no	jlam	1	-2/+2
	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.
2005-11-23	Initial import of p5-Test-Tester:	wiz	4	-0/+24
	If you have written a test module based on Test::Builder then Test::Tester allows you to test it with the minimum of effort.