ports/86098: [PATCH] devel/pear-PEAR/Makefile.common: allow use by foreign packages
neuhauser at sigpipe.cz
Wed Sep 14 01:20:01 UTC 2005
>Synopsis: [PATCH] devel/pear-PEAR/Makefile.common: allow use by foreign packages
>Arrival-Date: Wed Sep 14 01:20:00 GMT 2005
>Originator: Roman Neuhauser
>Release: FreeBSD 4.10-STABLE i386
The attached patch allows ports for packages from outside pear.php.net
use devel/pear-PEAR/Makefile.common by only setting MASTER_SITES et al.
when PEAR_ALIEN is not defined.
A bit of background:
I received a PR updating devel/simpletest I maintain from (a year old)
1.0RC1 to 1.0.
The author of SimpleTest released two tarballs for the 1.0 version, one
of them constitutes a pear(1) installable package (contains package.xml;
alas, misses the documentation, but that's beside the point), and the
submitter of the PR chose to base the patch on the pear compatible
tarball and .included Makefile.common (previous version of
devel/simpletest/Makefile had pieces of it copypasted).
That created a problem: Makefile.common sets MASTER_SITES etc.
unconditionally. That's easily fixed, but this patch made me think:
should pearified but non-pear.php.net packages acquire the pear-
PKGNAMEPREFIX or not? Porter's Handbook says
pear* Ports related to the Pear PHP framework.
but how much is software like SimpleTest related? I guess it should
have the prefix, it installs under /usr/local/share/pear after all..
I don't really have an opinion, but the ability to use the
Makefile.common code in ports for packages coming from outside
pear.php.net is nice with or without PKGNAMEPREFIX.
--- devel::pear-PEAR::Makefile.common-PEAR_ALIEN,0.patch begins here ---
RCS file: /home/ncvs/ports/devel/pear-PEAR/Makefile.common,v
retrieving revision 1.13
diff -u -r1.13 Makefile.common
--- devel/pear-PEAR/Makefile.common 21 Feb 2005 18:05:04 -0000 1.13
+++ devel/pear-PEAR/Makefile.common 13 Sep 2005 23:51:09 -0000
@@ -2,12 +2,14 @@
# Common code for pear- ports.
--- devel::pear-PEAR::Makefile.common-PEAR_ALIEN,0.patch ends here ---
More information about the freebsd-ports-bugs