At the end of this message is a patch to move some stuff that is in
cpan.port.mk into perl.port.mk.
I have some perl ports that I am using internally, and these are things
I generally do whenever I have a perl port, even if it isn't on the
CPAN.
I am not sure that this doesn't break anything, I don't do bulk builds
or anything, but I didn't see anything straight off that would get
borked.
l8rZ,
--
andrew - ICQ# 253198 - Jabber: [EMAIL PROTECTED]
BOFH excuse of the day: Incorrect time synchronization
Index: cpan.port.mk
===================================================================
RCS file: /cvs/ports/infrastructure/mk/cpan.port.mk,v
retrieving revision 1.6
diff -u -r1.6 cpan.port.mk
--- cpan.port.mk 28 Jan 2008 00:03:01 -0000 1.6
+++ cpan.port.mk 26 Mar 2008 17:43:51 -0000
@@ -1,6 +1,5 @@
# $OpenBSD: cpan.port.mk,v 1.6 2008/01/28 00:03:01 simon Exp $
-PKGNAME?= p5-${DISTNAME}
.if !defined(CPAN_AUTHOR)
MASTER_SITES?= ${MASTER_SITE_PERL_CPAN:=${DISTNAME:C/-.*$//}/}
.else
@@ -8,7 +7,6 @@
.endif
CATEGORIES+= perl5
-CONFIGURE_STYLE+=perl
MODULES+= perl
REGRESS_DEPENDS+=${RUN_DEPENDS}
Index: perl.port.mk
===================================================================
RCS file: /cvs/ports/infrastructure/mk/perl.port.mk,v
retrieving revision 1.13
diff -u -r1.13 perl.port.mk
--- perl.port.mk 22 May 2007 20:57:25 -0000 1.13
+++ perl.port.mk 26 Mar 2008 17:43:51 -0000
@@ -4,8 +4,10 @@
# Based on bsd.port.mk, originally by Jordan K. Hubbard.
# This file is in the public domain.
-REGRESS_TARGET ?= test
-MODPERL_BUILD ?= Build
+REGRESS_TARGET ?= test
+MODPERL_BUILD ?= Build
+PKGNAME ?= p5-${DISTNAME}
+CONFIGURE_STYLE += perl
.if ${CONFIGURE_STYLE:L:Mmodbuild}
. if !${PKGPATH:M*devel/p5-Module-Build}
