ports/86098: [PATCH] devel/pear-PEAR/Makefile.common: allow use by foreign packages

[Roman Neuhauser]

The following reply was made to PR ports/86098; it has been noted by GNATS.

From: Roman Neuhauser <neuhauser at sigpipe.cz>
To: Antonio Carlos Venancio Junior <antonio at php.net>
Cc: freebsd-ports-bugs at FreeBSD.org, bug-followup at FreeBSD.org,
	Pav Lucistnik <pav at FreeBSD.org>, Thierry Thomas <thierry at FreeBSD.org>
Subject: Re: ports/86098: [PATCH] devel/pear-PEAR/Makefile.common: allow use by foreign packages
Date: Thu, 15 Sep 2005 14:26:50 +0200

 # antonio at php.net / 2005-09-15 09:10:11 -0300:
 > Roman Neuhauser wrote:
 > ># antonio at php.net / 2005-09-14 19:15:46 -0300:
 > >>Roman Neuhauser wrote:
 > >>># antonio at php.net / 2005-09-14 18:14:16 -0300:
 > >>>>	SimpleTest isn't a PEAR package and I don't think it's a good idea 
 > >>>>	have "alien" packages using Makefile.common.
 > >>>
 > >>>  Why?
 > >>
 > >>	Because it's not part of the PEAR PHP Framework.
 > >
 > >    Is there a *technical* reason?
 > 
 > 	No. It's a semantical reason.
 
     Ok, putting Makefile.common aside for a while, what's everybody's
     position on these two questions (simple yes/no will do):
 
     * should pear-compatible packages that don't come from pear.php.net
       get installed under ${PEARDIR}?
 
     * should pear-compatible packages that don't come from pear.php.net
       get "PKGNAMEPREFIX=pear-"?
 
 > 	Keep in mind that you will have to chosse between pear-* ports 
 > structure or the PEAR CLI.
 
     Then I wonder why we bother with installing package.xml files.
 
 -- 
 How many Vietnam vets does it take to screw in a light bulb?
 You don't know, man.  You don't KNOW.
 Cause you weren't THERE.             http://bash.org/?255991