Home > Archive > PHP Pear > July 2005 > Re: [PEAR] Best practice for multiple pear installations?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Re: [PEAR] Best practice for multiple pear installations?
|
|
| Jan Wagner 2005-07-27, 9:03 am |
| > what is a good/best practive to handle multiple PEAR installations?
Funny thing is, I tried just that today ;-)
> Currently on my system there's the system-wide installation from the
> debian package in /usr/share/php .
>
> Using 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 w s 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.
Cheers Jan
| |
| Markus Fischer 2005-07-28, 4:01 am |
| Jan Wagner wrote:
>
>
> 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.
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,
- Markus
| |
| Markus Fischer 2005-07-28, 4:01 am |
| Jan Wagner wrote:
>
>
> 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.
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,
- Markus
| |
| Markus Fischer 2005-07-28, 4:01 am |
| Jan Wagner wrote:
>
>
> 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.
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,
- Markus
|
|
|
|
|