pkgsrc/devel/p5-ExtUtils-F77/Makefile

# $NetBSD: Makefile,v 1.14 2006/03/04 21:29:21 jlam Exp $

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

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

PKG_INSTALLATION_TYPES=	overwrite pkgviews

PERL5_PACKLIST=		auto/ExtUtils/F77/.packlist

.include "../../lang/perl5/module.mk"
.include "../../mk/bsd.pkg.mk"
Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where no developer is officially maintaining the package. The rationale for changing this from "tech-pkg" to "pkgsrc-users" is that it implies that any user can try to maintain the package (by submitting patches to the mailing list). Since the folks most likely to care about the package are the folks that want to use it or are already using it, this would leverage the energy of users who aren't developers. 2006-03-04 22:28:51 +01:00			`# $NetBSD: Makefile,v 1.14 2006/03/04 21:29:21 jlam 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`
Bump the PKGREVISIONs of all (638) packages that hardcode the locations of Perl files to deal with the perl-5.8.7 update that moved all pkgsrc-installed Perl files into the "vendor" directories. 2005-08-06 08:19:03 +02:00			`PKGREVISION= 2`
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/}`

Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where no developer is officially maintaining the package. The rationale for changing this from "tech-pkg" to "pkgsrc-users" is that it implies that any user can try to maintain the package (by submitting patches to the mailing list). Since the folks most likely to care about the package are the folks that want to use it or are already using it, this would leverage the energy of users who aren't developers. 2006-03-04 22:28:51 +01:00			`MAINTAINER= pkgsrc-users@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
Bl3ify and enable pkgviews installation. 2004-04-25 05:49:09 +02:00			`PKG_INSTALLATION_TYPES= overwrite pkgviews`

Turn PERL5_PACKLIST into a relative path instead of an absolute path. These paths are now relative to PERL5_PACKLIST_DIR, which currently defaults to ${PERL5_SITEARCH}. There is no change to the binary packages. 2005-07-13 20:01:18 +02:00			`PERL5_PACKLIST= 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"`