Re: PHP build --with-pear fails: conflict over /tmp/pear/cache

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



Keith Roberts <keith@xxxxxxxxxxxx> wrote:
> I used to compile PHP without any --with/out-pear 
> ./configure options. This installed PEAR under the 
> --prefix=/usr/local/php-5.x.x directory path.

> So everytime I upgraded PHP, I got a fresh installation of 
> PEAR in a different location. I now have PEAR installed 

More often than not, I'm doing a new build of the same version of PHP
with different configure options to support something we didn't need
in the past but do now, so I can't depend on a new version number.

However, my php builds always install in /usr/local/lib/php/ without a
version number.  During the build, they install in a temporary location
that I (or my rpmbuild script) gives them.  For example,
  make INSTALL_ROOT=/foo install
Places it in /foo/usr/local/lib/php.

However, it's still configured to work as though everything is under
/usr/local/bin so when I actually install the RPM, which puts files
there, everything looks like a default install.  That's pretty standard.

In the past, php didn't have any problems with this method.

> You need to check what config files are being used by each 
> installation of PEAR. They are quite possibly different. So 
> another PEAR installation in a different location should use 
> it's own set of config files.

My goal, however, is to have each installation of PEAR in the *SAME*
directory.  When the resulting RPM is installed on the system, it
should replace whatever was there before.  Other files and scripts
should not have to be updated - they should expect things to be in the
same (default) locations.

> I cannot see any problems with using a different 
> --with-pear=/new/path for testing purposes.

Right, but what about for production purposes?  It should use
/tmp/pear in a production install, it just should honor the temporary
install root when building (and only when building).

It feels like something is broken in PHP's Makefile or whatever pear
install procedures it runs, that used to not be broken, but it may be
some difference in my system environment since the last time I built a
PHP RPM, that I'm not guessing is related.
  -- Cos

[Index of Archives]     [PHP Users]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [Postgresql]     [PHP Books]     [PHP Databases]     [PHP SOAP]
  Powered by Linux