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

# $OpenBSD: Makefile,v 1.6 2008/04/15 22:09:06 jasper Exp $

COMMENT=		interact with a t/test_manifest file

MODULES=		cpan
DISTNAME=		Test-Manifest-1.22
CATEGORIES=		devel

MAINTAINER=		Jasper Lievisse Adriaanse <jasper@openbsd.org>

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

MAKE_ENV=		TEST_POD=Yes

.include <bsd.port.mk>
- update Test::Manifest to 1.22 2008-04-15 18:09:06 -04:00			`# $OpenBSD: Makefile,v 1.6 2008/04/15 22:09:06 jasper Exp $`
import p5-Test-Manifest-1.14 Test::Manifest overrides the default behaviour by replacing the test_via_harness target in the Makefile. Instead of running at the t/*.t files in ascii-betical order, it looks in the t/test_manifest file to find out which tests you want to run and the order in which you want to run them. It constructs the right value for MakeMaker to do the right thing. submitted by Jasper Lievisse Adriaanse <jasper at nedbsd.nl> ok alek@ 2005-12-13 16:46:43 -05:00
Remove quotes surrounding COMMENT/PERMIT_/BROKEN 2007-09-15 22:52:56 -04:00			`COMMENT= interact with a t/test_manifest file`
switch everyone left in devel to cpan 2006-11-29 03:23:29 -05:00
			`MODULES= cpan`
- update Test::Manifest to 1.22 2008-04-15 18:09:06 -04:00			`DISTNAME= Test-Manifest-1.22`
switch everyone left in devel to cpan 2006-11-29 03:23:29 -05:00			`CATEGORIES= devel`
import p5-Test-Manifest-1.14 Test::Manifest overrides the default behaviour by replacing the test_via_harness target in the Makefile. Instead of running at the t/*.t files in ascii-betical order, it looks in the t/test_manifest file to find out which tests you want to run and the order in which you want to run them. It constructs the right value for MakeMaker to do the right thing. submitted by Jasper Lievisse Adriaanse <jasper at nedbsd.nl> ok alek@ 2005-12-13 16:46:43 -05:00
update to 1.17 2007-03-17 18:41:07 -04:00			`MAINTAINER= Jasper Lievisse Adriaanse <jasper@openbsd.org>`
import p5-Test-Manifest-1.14 Test::Manifest overrides the default behaviour by replacing the test_via_harness target in the Makefile. Instead of running at the t/*.t files in ascii-betical order, it looks in the t/test_manifest file to find out which tests you want to run and the order in which you want to run them. It constructs the right value for MakeMaker to do the right thing. submitted by Jasper Lievisse Adriaanse <jasper at nedbsd.nl> ok alek@ 2005-12-13 16:46:43 -05:00
			`# GPL/Artistic`
			`PERMIT_PACKAGE_FTP= Yes`
			`PERMIT_PACKAGE_CDROM= Yes`
			`PERMIT_DISTFILES_FTP= Yes`
			`PERMIT_DISTFILES_CDROM= Yes`

switch everyone left in devel to cpan 2006-11-29 03:23:29 -05:00			`MAKE_ENV= TEST_POD=Yes`
import p5-Test-Manifest-1.14 Test::Manifest overrides the default behaviour by replacing the test_via_harness target in the Makefile. Instead of running at the t/*.t files in ascii-betical order, it looks in the t/test_manifest file to find out which tests you want to run and the order in which you want to run them. It constructs the right value for MakeMaker to do the right thing. submitted by Jasper Lievisse Adriaanse <jasper at nedbsd.nl> ok alek@ 2005-12-13 16:46:43 -05:00
			`.include <bsd.port.mk>`