Re: Relocating a pear installation

On 9/7/06, Markus Fischer <markus@fischer.name> wrote:

Greg Beaver wrote:

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. Hmm .. really? I mean, when I relocate my pear installation (= physically moving files around) my data dir goes with it, so this should , and in my case, does work. Or did I understood you wrongly?

The problem is that the PEAR installer supports replacements at install time and one of these replacements is the data dir. When installed the scripts get an absolute path to the data dir. If the package isn't smart enough to have a fallback it will fail to find its data. -- Justin Patrin