Re: go-pear doesn't like env vars
| From: | bertrand Gugger | Date: | Wed, 04 Jan 2006 07:33:49 +0000 |
| Subject: | Re: go-pear doesn't like env vars | ||
| References: | 1 | Groups: | php.pear.general |
| Request: | Send a blank email to pear-general+get-22426@lists.php.net to get a copy of this message | ||
Bonjour
Maarten van Dantzich wrote:
1. Installation prefix : /usr/local 2. Binaries directory : [Installation prefix]/bin Anyway, it makes *always* sense to use the bug tracker, eventually being put "bogus" is no infamy. In anycase, that let usefull information for the next one that will be trapped as you was. Now in your particular case, the change you suggest is a minimum, I agree the current formulation can lead to some confusion. But your request to have go-pear interpret eventual ENV variables in the layout definition is of value and should not be rejected without some explanations or indications on how to turn around it. my 2 cts, a+ -- togggENV vars are normally expanded by your shell. AFAIK, PHP has no built-in way to expand ENV vars within a script. This should probably be mentioned somewhere in the manual...care to give us quick patch to the docs?It makes more sense to me to fix the problem than to document it somewhere. Would it be reasonable for me to file a bug and request that go-pear not use the "$prefix" phrasing in the path names it presents? Currently it says:but instead would be modified to say something like:1. Installation prefix : /usr/local 2. Binaries directory : $prefix/binTo be coherent then:1. Installation prefix : /usr/local 2. Binaries directory : [install dir]/bin