Re: PHP 5.0.5 and PEAR 1.4.2...together?

Andrew Teixeira wrote: > I have found one more problem that may or may not be serious when > installing PEAR in this manner. As I said in my previous post, I was > able to get PEAR and all the new versions of the PEAR modules included > in PHP's source installed, but now whenever I do "pear list > <package>", the file locations are listed as > "/tmp/php-buildroot/usr/lib/php/xxxxxx" instead of > "/usr/lib/php/xxxxxx". I tested this on a new package (DB) by using > the following command-line: > > pear install --nodeps -R /tmp/junk/DB-1.7.6.tgz > > to try to use PEAR itself to install a module to another directory. > This leads to the same problem (i.e. files listed as > /tmp/junk/usr/lib/php/xxxxx). My question now is whether I am > misunderstanding pear install's -R option or if PEAR is somehow > broken. I would assume that the -R is there specifically for > situations such as mine where you want to compile PHP/PECL/PEAR to > live in a certain directory, but you have to temporarily install the > files somewhere else (e.g. for RPM packaging). I believe the older > versions of PEAR worked in this manner (i.e. 1.3.x in the PHP source > never seemed to have this problem), so I'm not sure if it is a bug or > a change in the way pear operates. Help would be greatly appreciated > since this also affects my building of secondary RPM packages using > PEAR as well. > > Any help would be greatly appreciated. See: http://greg.chiaraquartet.net/archives/93-re-distributing-PEARPHP-outside-of-php.net-an-important-tip-and-open-question.html For my take on the situation. Thanks, Greg