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

# Created by: Sunpoet Po-Chuan Hsieh <sunpoet@FreeBSD.org>
# $FreeBSD$

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

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

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

USE_PERL5=	configure
USES=		perl5

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

.include <bsd.port.mk>
- Cleanup Makefile header 2013-08-21 19:42:57 +02:00			`# Created by: Sunpoet Po-Chuan Hsieh <sunpoet@FreeBSD.org>`
- 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			`# $FreeBSD$`

			`PORTNAME= POE-Loop-Tk`
- Update to 1.305 Changes: http://search.cpan.org/dist/POE-Loop-Tk/CHANGES 2013-08-22 19:38:50 +02:00			`PORTVERSION= 1.305`
Change the way Perl modules are installed, update the default Perl to 5.18. Before, we had: site_perl : lib/perl5/site_perl/5.18 site_perl/perl_arch : lib/perl5/site_perl/5.18/mach perl_man3 : lib/perl5/5.18/man/man3 Now we have: site_perl : lib/perl5/site_perl site_arch : lib/perl5/site_perl/mach/5.18 perl_man3 : lib/perl5/site_perl/man/man3 Modules without any .so will be installed at the same place regardless of the Perl version, minimizing the upgrade when the major Perl version is changed. It uses a version dependent directory for modules with compiled bits. As PERL_ARCH is no longer needed in plists, it has been removed from PLIST_SUB. The USE_PERL5=fixpacklist keyword is removed, the .packlist file is now always removed, as is perllocal.pod. The old site_perl and site_perl/arch directories have been kept in the default Perl @INC for all Perl ports, and will be phased out as these old Perl versions expire. PR: 194969 Differential Revision: https://reviews.freebsd.org/D1019 Exp-run by: antoine Reviewed by: perl@ Approved by: portmgr 2014-11-26 14:08:24 +01:00			`PORTREVISION= 2`
- 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`
- Remove leading indefinite article from COMMENT 2013-08-21 19:17:25 +02:00			`COMMENT= Bridge that allows POE to be driven by Tk`
- 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
- Update to 1.305 Changes: http://search.cpan.org/dist/POE-Loop-Tk/CHANGES 2013-08-22 19:38:50 +02:00			`BUILD_DEPENDS= p5-POE>=1.356:${PORTSDIR}/devel/p5-POE \`
			`p5-Tk>=804.031:${PORTSDIR}/x11-toolkits/p5-Tk`
- Use RUN_DEPENDS:=BUILD_DEPENDS - Add BUILD_DEPENDS - Cosmetic change 2013-08-21 16:55:43 +02:00			`RUN_DEPENDS:= ${BUILD_DEPENDS}`
- 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
- Convert to new perl framework 2013-08-21 16:08:06 +02:00			`USE_PERL5= configure`
			`USES= perl5`
- 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
			`post-patch:`
			`@${REINPLACE_CMD} -e '/POE::Test::Loops/d' ${WRKSRC}/Makefile.PL`

			`.include <bsd.port.mk>`