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

[Antonio Carlos Venancio Junior]

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

From: Antonio Carlos Venancio Junior <antonio at php.net>
To: Roman Neuhauser <neuhauser at sigpipe.cz>
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 09:10:11 -0300

 Roman,
 
 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.
 
 > 
 >>The author should follow the formal proposal process 
 >>(http://pear.php.net/manual/en/newmaint.proposal.php) to have his 
 >>package added to the framework.
 > 
 > 
 >     No, there's just no reason. That's like saying that people shouldn't
 >     create packages for use with pkg_add unless the ports are in FreeBSD
 >     proper. pear.php.net supports alien packages, see the bottom of
 >     http://pear.php.net/packages.php
 > 
 > 
 >>	Try to have a look at devel/beautifyphp.
 > 
 >  
 >     Anything particular to look for?
 > 
 > 
 >>>>Besides that, this port should not install files inside
 >>>>/usr/local/share/pear ...
 >>>
 >>>
 >>>   Ok, where does pear(1) normally put e. g. Horde when you install it
 >>>   using their package.xml files?
 >>
 >>	The Horde port installs its required PEAR packages via RUN_DEPENDS. 
 > 
 > 
 >     Ignore ports for a while. Go to http://pear.php.net/channels/,
 >     follow the link to http://pear.horde.org/, and install Horde_VFS
 >     using the procedure described there, which is:
 > 
 >     pear install http://pear.horde.org/Horde_VFS-0.0.1.tgz
 > 
 >     Where will it be installed (on FreeBSD, with PHP / pear(1) from ports)?
 > 
 > 
 >>When you install that packages using pear(1) directly it would place 
 >>them inside the php_dir (defaults to /usr/lib/php).
 > 
 > 
 >     Well, it's /usr/local/lib/php/pear on this box (php4-pear-4.3.11_1),
 >     which means ports-installed pear puts packages in a directory that's
 >     not in include_path, and that smells like a bug, but...
 
 	Yes and that's not a bug. There's a message telling you to add that dir 
 to your PHP include path when you install PEAR via ports [1].
 	If you follow the docs/INSTALL [2] (3.3 Additional PEAR Modules) file 
 you will see that required PEAR packages are installed using a remote 
 package. That's exactly what the Horde port does.
 	When you are using a port you have to install the files following the 
 FreeBSD directory standards [3]. That's why PEAR is installed inside 
 ${PREFIX}/share/pear.
 	Keep in mind that you will have to chosse between pear-* ports 
 structure or the PEAR CLI.
 
 [1] 
 http://www.freebsd.org/cgi/cvsweb.cgi/ports/lang/php4/pkg-message.pear?rev=1.1&content-type=text/x-cvsweb-markup
 [2] http://www.horde.org/horde/docs/?f=INSTALL.html#quick-install
 [3] http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/
 
 -- 
 Cya
 
 Antonio
 echo antonio php net | sed 's/ /@/;s/ /./g'
 FreeBSD/OpenBSD | PHP/MySQL | PGP Key ID 0x5BBEB073
 "Can't buy what I want because its FREE!" - Pearl Jam