freebsd-ports/devel/p5-POE-Loop-Tk/Makefile

# New ports collection makefile for:	p5-POE-Loop-Tk
# Date created:		2011-10-10
# Whom:			Sunpoet Po-Chuan Hsieh <sunpoet@FreeBSD.org>
#
# $FreeBSD$
#

PORTNAME=	POE-Loop-Tk
PORTVERSION=	1.304
PORTREVISION=	1
CATEGORIES=	devel tk perl5
MASTER_SITES=	CPAN
PKGNAMEPREFIX=	p5-

MAINTAINER=	sunpoet@FreeBSD.org
COMMENT=	A bridge that allows POE to be driven by Tk

BUILD_DEPENDS=	p5-POE>=1.289:${PORTSDIR}/devel/p5-POE \
		p5-Tk>=804.028:${PORTSDIR}/x11-toolkits/p5-Tk
RUN_DEPENDS=	p5-POE>=1.289:${PORTSDIR}/devel/p5-POE \
		p5-Tk>=804.028:${PORTSDIR}/x11-toolkits/p5-Tk

PERL_CONFIGURE=	yes

MAN3=		POE::Loop::Tk.3 \
		POE::Loop::TkActiveState.3 \
		POE::Loop::TkCommon.3

post-patch:
	@${REINPLACE_CMD} -e '/POE::Test::Loops/d' ${WRKSRC}/Makefile.PL

.include <bsd.port.mk>
- Add p5-POE-Loop-Tk 1.304 POE::Loop::Tk implements the interface documented in POE::Loop. Therefore it has no documentation of its own. Please see POE::Loop for more details. POE::Loop::Tk is one of two versions of the Tk event loop bridge. The other, POE::Loop::TkActiveState accommodates behavior differences in ActiveState's build of Tk. Both versions share common code in POE::Loop::TkCommon. POE::Loop::Tk dynamically selects the appropriate bridge code based on the runtime enviroment. WWW: http://search.cpan.org/dist/POE-Loop-Tk/ 2011-10-15 18:32:01 +02:00			`# New ports collection makefile for: p5-POE-Loop-Tk`
			`# Date created: 2011-10-10`
			`# Whom: Sunpoet Po-Chuan Hsieh <sunpoet@FreeBSD.org>`
			`#`
			`# $FreeBSD$`
			`#`

			`PORTNAME= POE-Loop-Tk`
			`PORTVERSION= 1.304`
- update png to 1.5.10 2012-06-01 07:26:28 +02:00			`PORTREVISION= 1`
- Add p5-POE-Loop-Tk 1.304 POE::Loop::Tk implements the interface documented in POE::Loop. Therefore it has no documentation of its own. Please see POE::Loop for more details. POE::Loop::Tk is one of two versions of the Tk event loop bridge. The other, POE::Loop::TkActiveState accommodates behavior differences in ActiveState's build of Tk. Both versions share common code in POE::Loop::TkCommon. POE::Loop::Tk dynamically selects the appropriate bridge code based on the runtime enviroment. WWW: http://search.cpan.org/dist/POE-Loop-Tk/ 2011-10-15 18:32:01 +02:00			`CATEGORIES= devel tk perl5`
			`MASTER_SITES= CPAN`
			`PKGNAMEPREFIX= p5-`

			`MAINTAINER= sunpoet@FreeBSD.org`
			`COMMENT= A bridge that allows POE to be driven by Tk`

			`BUILD_DEPENDS= p5-POE>=1.289:${PORTSDIR}/devel/p5-POE \`
			`p5-Tk>=804.028:${PORTSDIR}/x11-toolkits/p5-Tk`
			`RUN_DEPENDS= p5-POE>=1.289:${PORTSDIR}/devel/p5-POE \`
			`p5-Tk>=804.028:${PORTSDIR}/x11-toolkits/p5-Tk`

			`PERL_CONFIGURE= yes`

			`MAN3= POE::Loop::Tk.3 \`
			`POE::Loop::TkActiveState.3 \`
			`POE::Loop::TkCommon.3`

			`post-patch:`
			`@${REINPLACE_CMD} -e '/POE::Test::Loops/d' ${WRKSRC}/Makefile.PL`

			`.include <bsd.port.mk>`