Re: Best practice for multiple pear installations?
| From: | Markus Fischer | Date: | Thu, 28 Jul 2005 07:25:43 +0000 |
| Subject: | Re: Best practice for multiple pear installations? | ||
| References: | 1 2 | Groups: | php.pear.general |
| Request: | Send a blank email to pear-general+get-20176@lists.php.net to get a copy of this message | ||
Jan Wagner wrote:
Thanks, that explains it. I tried a new installation and there was a ~/.pearrc ( which for some clever reason I obviously deleted in the past, maybe thinking it was from another installation). Thank you, - MarkusUsing go-pear I already created my own repository, /data/www/webroot/pear and by calling /data/www/webroot/pear/bin/pear it worked quite well. Now a few weeks alter, just calling /data/www/webroot/pear/bin/pear revealed that it was not using my new repository but reverted to the default system wide which I don't want.That is how I do it, almost. Save your old /usr/bin/pear and ~/.pearrc before installing go-pear into your webroot. Then move the new .pearrc to webroot and call webroot/pear/bin/pear -c /wherever/you/moved/your/new/.pearrc. Move your saved /usr/bin/pear and .pearrc back (I think the debian package uses /etc/pear/pear.conf for the default /usr/bin/pear, so no .pearrc should be there). That works fine here.