openbsd-ports/devel/p5-Test-Taint/Makefile

# $OpenBSD: Makefile,v 1.10 2010/12/03 11:44:37 ajacoutot Exp $

SHARED_ONLY=	Yes

COMMENT= 	tools to test taintedness

MODULES=	cpan
DISTNAME=	Test-Taint-1.04
REVISION=	4
CATEGORIES=	devel
USE_GROFF =	Yes

# Artistic
PERMIT_PACKAGE_CDROM=	Yes
PERMIT_PACKAGE_FTP=	Yes
PERMIT_DISTFILES_CDROM=	Yes
PERMIT_DISTFILES_FTP=	Yes

MAKE_ENV=	TEST_POD=Yes

.include <bsd.port.mk>
Bump after recent cpan.port.mk change. ok jasper@ 2010-12-03 06:44:22 -05:00			`# $OpenBSD: Makefile,v 1.10 2010/12/03 11:44:37 ajacoutot Exp $`
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
- NOT_FOR_ARCHS = NO_SHARED_ARCHS -> SHARED_ONLY - update to 1.04 2004-12-20 21:51:21 -05:00			`SHARED_ONLY= Yes`
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
Remove quotes surrounding COMMENT/PERMIT_/BROKEN 2007-09-15 22:52:56 -04:00			`COMMENT= tools to test taintedness`
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
switch everyone left in devel to cpan 2006-11-29 03:23:29 -05:00			`MODULES= cpan`
- NOT_FOR_ARCHS = NO_SHARED_ARCHS -> SHARED_ONLY - update to 1.04 2004-12-20 21:51:21 -05:00			`DISTNAME= Test-Taint-1.04`
Bump after recent cpan.port.mk change. ok jasper@ 2010-12-03 06:44:22 -05:00			`REVISION= 4`
switch everyone left in devel to cpan 2006-11-29 03:23:29 -05:00			`CATEGORIES= devel`
USE_GROFF=Yes 2010-10-18 13:47:50 -04:00			`USE_GROFF = Yes`
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
			`# Artistic`
			`PERMIT_PACKAGE_CDROM= Yes`
			`PERMIT_PACKAGE_FTP= Yes`
			`PERMIT_DISTFILES_CDROM= Yes`
			`PERMIT_DISTFILES_FTP= Yes`

switch everyone left in devel to cpan 2006-11-29 03:23:29 -05:00			`MAKE_ENV= TEST_POD=Yes`
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
			`.include <bsd.port.mk>`