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.
This commit is contained in:
msf 2004-06-10 01:36:18 +00:00
parent f3bf9b3fb8
commit eb55a3f2d9
4 changed files with 46 additions and 0 deletions

View File

@ -0,0 +1,27 @@
# $OpenBSD: Makefile,v 1.1.1.1 2004/06/10 01:36:18 msf Exp $
NOT_FOR_ARCHS= ${NO_SHARED_ARCHS}
COMMENT= "tools to test taintedness"
DISTNAME= Test-Taint-1.02
PKGNAME= p5-${DISTNAME}
CATEGORIES= devel perl5
MAINTAINER= Mathieu Sauve-Frankel <msf@openbsd.org>
# Artistic
PERMIT_PACKAGE_CDROM= Yes
PERMIT_PACKAGE_FTP= Yes
PERMIT_DISTFILES_CDROM= Yes
PERMIT_DISTFILES_FTP= Yes
MASTER_SITES= ${MASTER_SITE_PERL_CPAN:=Test/}
REGRESS_DEPENDS= ::devel/p5-Test-Pod-Coverage
CONFIGURE_STYLE= perl
PKG_ARCH= *
.include <bsd.port.mk>

View File

@ -0,0 +1,3 @@
MD5 (Test-Taint-1.02.tar.gz) = ffd7c70c4c44e5b8124d8d291a5de802
RMD160 (Test-Taint-1.02.tar.gz) = cae5a750dc74d3993ba1f9974ce10d2077bf2942
SHA1 (Test-Taint-1.02.tar.gz) = 41f238fa5241f2204a1b66efa8452b81f6b9802e

View File

@ -0,0 +1,4 @@
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.

View File

@ -0,0 +1,12 @@
@comment $OpenBSD: PLIST,v 1.1.1.1 2004/06/10 01:36:18 msf Exp $
${P5ARCH}/Test/Taint.pm
@comment ${P5ARCH}/auto/Test/Taint/.packlist
${P5ARCH}/auto/Test/Taint/Taint.bs
${P5ARCH}/auto/Test/Taint/Taint.so
man/man3p/Test::Taint.3p
@dirrm man/man3p
@dirrm ${P5ARCH}/auto/Test/Taint
@dirrm ${P5ARCH}/auto/Test
@dirrm ${P5ARCH}/auto
@dirrm ${P5ARCH}/Test
@dirrm ${P5ARCH}