Re: Relocating a pear installation
| From: | Markus Fischer | Date: | Thu, 07 Sep 2006 18:16:38 +0000 |
| Subject: | Re: Relocating a pear installation | ||
| References: | 1 2 3 4 5 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-43914@lists.php.net to get a copy of this message | ||
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
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?
- - Markus
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFAGIF1nS0RcInK9ARAnvsAJ49YZQtODUDSFVkzNT4pHbHUnev5gCfXfdk
EDG1RiWjFryVTG2c3m8VjdM=
=St6f
-----END PGP SIGNATURE-----