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

Any news on this yet? I downloaded 5.1.1 and the installation works great, but there are 2 problems: 1. All files listed in the PEAR packages installed using the PHP installation process (PEAR, Archive_Tar, & Console_Getopt) are prefixed with the buildroot I used when making the RPM (/tmp/php-buildroot/usr/lib/php/Console/Getopt.php, etc.). This most likely links to what was previously discussed and what you posted that open question regarding. 2. I am trying to install PEAR packages in an RPM using the following command during a %post: pear install --nodeps -r /path/to/package.xml as was described in several pages I found. The problem is that if I do this, the module is installed fine (i.e. all files are in place and 'pear list' shows the module installed), but when I do 'pear list <packagename>', I get: [----screen----] Notice: Undefined index: data in PEAR/Frontend/CLI.php on line 681 Warning: Invalid argument supplied for foreach() in PEAR/Frontend/CLI.php on line 699 [----screen----] and no files are listed. I put a stub in CLI.php on line 680 to see what was in $data['data'] and find that for other packages installed using PEAR, data is full of data, but when using the '-r' flag, this information doesn't seem to exist. I should also mention that this problem doesn't have anything to do with RPM packaging since I tried this just from the command line directly to where PEAR is supposed to live and the same problem existed. I'm not sure if this should be posted as a bug on pear.php.net or if this has something to do with 1. I look forward to figuring this out. P.S. Good work on the rest of PEAR 1.4.5...besides these 2 issues, I have had great success with the new version. Thanks... On 10/31/05, Greg Beaver <greg@chiaraquartet.net> wrote: > 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 >