Re: Relocating a pear installation
| From: | Greg Beaver | Date: | Thu, 07 Sep 2006 13:01:56 +0000 |
| Subject: | Re: Relocating a pear installation | ||
| References: | 1 2 3 4 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-43911@lists.php.net to get a copy of this message | ||
Markus Fischer wrote:
> 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.
The reason is that if you change data_dir in pearrc, phpDocumentor would
suddenly and mysteriously be unable to find templates. That would not
be so good.
:)
Greg