pkgsrc/devel/p5-IO-Stty/Makefile

# $NetBSD: Makefile,v 1.6 2001/11/26 06:49:51 jlam Exp $

DISTNAME=	IO-Stty-.02
PKGNAME=	p5-IO-stty-0.02
SVR4_PKGNAME=	p5ist
CATEGORIES=	devel perl5
MASTER_SITES=	${MASTER_SITE_PERL_CPAN:=IO/}

MAINTAINER=	packages@netbsd.org
COMMENT=	Perl class for I/O on tty devices

USE_BUILDLINK_ONLY=	YES
PERL5_PACKLIST=		${PERL5_SITEARCH}/auto/IO/Stty/.packlist

do-configure:
	@cd ${WRKSRC}; ${SETENV} ${MAKE_ENV} ${PERL5} Makefile.PL

.include "../../lang/perl5/buildlink.mk"
.include "../../mk/bsd.pkg.mk"
Buildlinkify, in the sense that only the perl headers are found in ${PREFIX} -- everything else is pickup up from ${BUILDLINK_DIR}. 2001-11-26 07:49:36 +01:00			`# $NetBSD: Makefile,v 1.6 2001/11/26 06:49:51 jlam Exp $`
Import opf p5-IO-Stty-.02, a perl module for futzing w/ TTYs. 2000-07-16 02:39:58 +02:00
			`DISTNAME= IO-Stty-.02`
fix pkgname - .02 is not a version our tools deal nice with 2000-07-16 19:11:18 +02:00			`PKGNAME= p5-IO-stty-0.02`
SVR4 packages have a limit of 9 chars for a package name. The automatic truncation in gensolpkg doesn't work for packages which have the same package name for the first 5-6 chars. e.g. amanda-server and amanda-client would be named amanda and amanda. Now, we add a SVR4_PKGNAME and use amacl for amanda-client and amase for amanda-server. All svr4 packages also have a vendor tag, so we have to reserve some chars for this tag, which is normaly 3 or 4 chars. Thats why we can only use 6 or 5 chars for SVR4_PKGNAME. I used 5 for all the packages, to give the vendor tag enough room. All p5-* packages and a few other packages have now a SVR4_PKGNAME. 2001-10-18 17:20:01 +02:00			`SVR4_PKGNAME= p5ist`
Import opf p5-IO-Stty-.02, a perl module for futzing w/ TTYs. 2000-07-16 02:39:58 +02:00			`CATEGORIES= devel perl5`
			`MASTER_SITES= ${MASTER_SITE_PERL_CPAN:=IO/}`

			`MAINTAINER= packages@netbsd.org`
Update to new COMMENT style: COMMENT var in Makefile instead of pkg/COMMENT. 2001-02-16 15:38:16 +01:00			`COMMENT= Perl class for I/O on tty devices`
Import opf p5-IO-Stty-.02, a perl module for futzing w/ TTYs. 2000-07-16 02:39:58 +02:00
Buildlinkify, in the sense that only the perl headers are found in ${PREFIX} -- everything else is pickup up from ${BUILDLINK_DIR}. 2001-11-26 07:49:36 +01:00			`USE_BUILDLINK_ONLY= YES`
			`PERL5_PACKLIST= ${PERL5_SITEARCH}/auto/IO/Stty/.packlist`
Import opf p5-IO-Stty-.02, a perl module for futzing w/ TTYs. 2000-07-16 02:39:58 +02:00
			`do-configure:`
Convert packages to use PERL5_PACKLIST (part 1). These were the easy ones to do, and each compiled and installed/de-installed apparently correctly. As a side effect of the dynamic PLIST, we no longer need to have separate -static and -shared PLISTs. It's now easier than ever to make a perl5 package for NetBSD :) 2000-08-27 09:10:59 +02:00			`@cd ${WRKSRC}; ${SETENV} ${MAKE_ENV} ${PERL5} Makefile.PL`
Import opf p5-IO-Stty-.02, a perl module for futzing w/ TTYs. 2000-07-16 02:39:58 +02:00
Buildlinkify, in the sense that only the perl headers are found in ${PREFIX} -- everything else is pickup up from ${BUILDLINK_DIR}. 2001-11-26 07:49:36 +01:00			`.include "../../lang/perl5/buildlink.mk"`
Import opf p5-IO-Stty-.02, a perl module for futzing w/ TTYs. 2000-07-16 02:39:58 +02:00			`.include "../../mk/bsd.pkg.mk"`