Re: Relocating a pear installation
| From: | Markus Fischer | Date: | Thu, 07 Sep 2006 05:28:59 +0000 |
| Subject: | Re: Relocating a pear installation | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-43909@lists.php.net to get a copy of this message | ||
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Markus Fischer wrote:
> Justin Patrin wrote:
>>> Well, you could write a simple PHP script to unserialize and walk
>>> through the array, fixing the paths.
>
> Ok, thanks. Is there any existing script to do that? If I would work on
> such a thing, would the PEAR community be interested in integrating this
> functionality?
>
>>> Or you could just reinstall...it's not *that* hard, is it?
>
> Well, do safely deploy our software we need to version everything, so
> also PEAR installation. We always need exact version and not the latest,
> we can't guarantee that it would work properly.
I've now gone through the process of relocated. Relocating the paths in
pearrc and the registry was a no-brainer, however there are so many
absolute paths scattered through induvidual package sources (e.h.
phpDocumentor) it's impossible to automate this process seriously. I
wonder why package authors have to rely on hardcoded paths inside the
source after installation of their package instead of getting this
infomration also e.g. from pearrc or similiar. It's probably that
packages want to be independent too, I guess. With this situation I
don't see a sane way providing a completely automated process.
- - Markus
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFE/64b1nS0RcInK9ARAqW6AKDCb5Zc4jAPoPP0deR82uf1OMSPwACgx2cD
7iLteMm62FQaXb9tLvC2h2I=
=PWR7
-----END PGP SIGNATURE-----