openbsd-ports/devel/p5-Test-Taint/pkg/PLIST

@comment $OpenBSD: PLIST,v 1.3 2004/09/14 23:44:00 espie Exp $
${P5ARCH}/
${P5ARCH}/Test/
${P5ARCH}/Test/Taint.pm
${P5ARCH}/auto/
${P5ARCH}/auto/Test/
${P5ARCH}/auto/Test/Taint/
${P5ARCH}/auto/Test/Taint/Taint.bs
${P5ARCH}/auto/Test/Taint/Taint.so
@man man/man3p/Test::Taint.3p
switch to new plist, killing a few install scripts along the way. 2004-09-14 19:43:54 -04:00			`@comment $OpenBSD: PLIST,v 1.3 2004/09/14 23:44:00 espie Exp $`
new plists 2004-08-10 04:10:13 -04:00			`${P5ARCH}/`
			`${P5ARCH}/Test/`
Initial import of Test-Taint-1.02 When you're writing unit tests for code that deals with tainted data, you'll want to have a way to provide tainted data for your routines to handle, and easy ways to check and report on the taintedness of your data, in standard Test::More style. 2004-06-09 21:36:18 -04:00			`${P5ARCH}/Test/Taint.pm`
new plists 2004-08-10 04:10:13 -04:00			`${P5ARCH}/auto/`
			`${P5ARCH}/auto/Test/`
			`${P5ARCH}/auto/Test/Taint/`
Initial import of Test-Taint-1.02 When you're writing unit tests for code that deals with tainted data, you'll want to have a way to provide tainted data for your routines to handle, and easy ways to check and report on the taintedness of your data, in standard Test::More style. 2004-06-09 21:36:18 -04:00			`${P5ARCH}/auto/Test/Taint/Taint.bs`
			`${P5ARCH}/auto/Test/Taint/Taint.so`
new plists 2004-08-10 04:10:13 -04:00			`@man man/man3p/Test::Taint.3p`