pkgsrc/devel/p5-ExtUtils-F77/Makefile

# $NetBSD: Makefile,v 1.8 2003/07/17 21:32:23 grant Exp $

DISTNAME=	ExtUtils-F77-1.13
PKGNAME=	p5-${DISTNAME}
SVR4_PKGNAME=	p5ext
CATEGORIES=	devel perl5
MASTER_SITES=	${MASTER_SITE_PERL_CPAN:=ExtUtils/}

MAINTAINER=	tech-pkg@NetBSD.org
COMMENT=	Perl module for determining how to link Fortran and C

USE_BUILDLINK2=		YES
PERL5_PACKLIST=		${PERL5_SITEARCH}/auto/ExtUtils/F77/.packlist

.include "../../lang/perl5/module.mk"
.include "../../mk/bsd.pkg.mk"
s/netbsd.org/NetBSD.org/ 2003-07-17 23:31:04 +02:00			`# $NetBSD: Makefile,v 1.8 2003/07/17 21:32:23 grant Exp $`
Initial import of new "p5-ExtUtils-F77" package: Perl module for determining how to link Fortran and C 2000-11-26 23:08:06 +01:00
			`DISTNAME= ExtUtils-F77-1.13`
			`PKGNAME= p5-${DISTNAME}`
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= p5ext`
Initial import of new "p5-ExtUtils-F77" package: Perl module for determining how to link Fortran and C 2000-11-26 23:08:06 +01:00			`CATEGORIES= devel perl5`
			`MASTER_SITES= ${MASTER_SITE_PERL_CPAN:=ExtUtils/}`

s/netbsd.org/NetBSD.org/ 2003-07-17 23:31:04 +02:00			`MAINTAINER= tech-pkg@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 module for determining how to link Fortran and C`
Initial import of new "p5-ExtUtils-F77" package: Perl module for determining how to link Fortran and C 2000-11-26 23:08:06 +01:00
Use buildlink2. Use perl5/module.mk. 2002-10-14 00:22:45 +02:00			`USE_BUILDLINK2= YES`
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			`PERL5_PACKLIST= ${PERL5_SITEARCH}/auto/ExtUtils/F77/.packlist`
Initial import of new "p5-ExtUtils-F77" package: Perl module for determining how to link Fortran and C 2000-11-26 23:08:06 +01:00
Use buildlink2. Use perl5/module.mk. 2002-10-14 00:22:45 +02:00			`.include "../../lang/perl5/module.mk"`
Initial import of new "p5-ExtUtils-F77" package: Perl module for determining how to link Fortran and C 2000-11-26 23:08:06 +01:00			`.include "../../mk/bsd.pkg.mk"`