Re: testing tarball of PEAR 1.7.0RC1 (not 1.7.0) uploaded

Carsten Wiedmann wrote: > Gregory Beaver schrieb: >>> It would be nice, if the installer set: >>> | www_dir to $_channelConfigInfo['php_dir']\www >>> and >>> | cfg_dir to $_channelConfigInfo['php_dir']\cfg >> >> Although this would be easy to do, it is not advisable because these >> directories are intended to be separate from the php files. > > Well, I think, you don't see the problem. > > My PEAR is installed at "/users/cwiedmann/pear", and that's the value of > $_channelConfigInfo['php_dir'] (the "PEAR directory"). > > Thus I have for example: > "/users/cwiedmann/pear/docs", "/users/cwiedmann/pear/data" and > "/users/cwiedmann/pear/tests" > > I have rights (read/write) in this directory, and the webserver too > (e.g. for the webinstaller). > > PHP_BINDIR is "/usr/local/bin" (default setting). In this directory, I > have only read/execute rights. > > Now, after an upgrade, I have additional this settings: > www_dir = /usr/local/bin/www > cfg_dir = /usr/local/bin/cfg > > > What happens if I install a package, which uses these new roles? The > installer can't create this configured directories or put files in this > directories. > > On Windows you have an additional problem: > "PHP_BINDIR" is allways set to "C:\php5". And that's in the most/many > installations a non existing directory. (And I have no rights to create > a subdirectory in "C:\") > > > All together, I think it's really better to (pre-)configure the > directorys in my example to: > www_dir = /users/cwiedmann/pear/www > cfg_dir = /users/cwiedmann/pear/cfg > > which is: > www_dir = $_channelConfigInfo['php_dir']\www > cfg_dir = $_channelConfigInfo['php_dir']\cfg Hi Carsten, I do understand the problem. What is tricky is that your default configuration (with no .pearrc or pear.conf) would install PHP files into /usr/local/lib/php/pear/php, cfg files into /usr/local/lib/php/pear/cfg and www files into /usr/local/lib/php/pear/www. Now, add a config file and change php_dir to /usr/local/lib/php/pear/php - the value it was at before. Now suddenly your cfg files are installed into /usr/local/lib/php/pear/php/cfg. In other words, what you're suggesting would introduce some wtf factor that is not a good idea. Pyrus and PEAR2 standards solves this problem from the beginning, but it is simply not possible to change this in PEAR without breaking BC with every existing version of PEAR. Greg