Re: RPM Packaging of PEAR-1.4.11.tgz

Rey Paderna wrote:

Hi - I beg the everyone's pardon if this isn't the correct list to post this question. In our current setup, we deploy PEAR packages via yum. All modules build fine with "pear rpm package.tgz". I'm having problems with the PEAR::PEAR package however. Build seems to go fine, but after installing, it seems to be using the buildroot path - "/var/tmp/php5-pear-root/usr/share/pear" and not the actual pear directory - "/usr/share/pear"

First, I would recommend installing PEAR_Command_Packaging if you haven't already. This is a fork (by me) of the original PEAR RPM code which is now deprecated (in fact, recent versions of PEAR raise a warning if you use "pear makerpm" or "pear rpm"). Second, the PEAR::PEAR package is a bit special in terms of RPM packaging. There was a discussion on here a while ago about it: http://www.zend.com/lists/pear-dev/200604/msg00153.html Now, that was actually about bootstrapping it from a clean environment, whereas you're building from an environment that already includes PEAR. I have to admit I haven't tried recently to see what "make-rpm-spec" does on an existing environment. However, try with PEAR_Command_Packaging as that has fixed many bugs from the original (core) PEAR code. That said, if you are using RHEL4 then I would just do what I do, and rebuild the php-pear package from Fedora. This does assume, however, that you want to use PHP5, since recent Fedora stuff depends on it. If you want to carry on using PHP4 then it might be slightly trickier. You will also find a number of other PEAR packages and related stuff (including an RPM for PEAR_Command_Packaging) in Fedora. I use EL4 too, so I'm using most of what I've been working on in both Fedora and EL4 environments. Tim