Re: Re: Question wrt dual-PEAR
| From: | Greg Beaver | Date: | Tue, 01 Feb 2005 04:17:24 +0000 |
| Subject: | Re: Re: Question wrt dual-PEAR | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-35842@lists.php.net to get a copy of this message | ||
Ian Eure wrote:
On Monday 31 January 2005 03:40 pm, Greg Beaver wrote:Sounds like they need to re-evaluate their policies? ;) Seriously though, the way PEAR works is there is a system configuration file and a user configuration file. If you want two installations of PEAR, the PEAR way is to have 2 configuration files, one for each installation. In this way, the PEAR installer elegantly allows install of local copies of a package. The debian package manager could easily wrap the pear command, as Alan Knowles suggests, and pass in a hard-coded user config file if it isn't specified on the command-line. In other words, the pear script would be called with pear -c /path/to/debian_usr_local_share/pear.conf $@ if the user did not pass in a command-line that overrides the default local pear.conf GregIf you wish a superuser to install, the best solution is to distribute a file with debian, /root/.pearrc. This file would define the install directories to be /usr/local/share/php/XXX. Creating this file is somewhat risky in the sense that some users may already have a .pearrc file in /root. Would debian be smart enough to not modify an existing .pearrc?I believe this violates Debian policy.