Re: Making local installations easier

Hi you two, This is fine - I agree it could be documented better. Would there be any objection to adding an alias of this nature: instead of: $ pear -c ~/.pearrc -d doc_dir=~/.pear/docs -d php_dir=~/.pear/PEAR -ext_dir=~/.pear/exts -d data_dir=~/.pear/data install Package The user could type: $ pear --local install Package which would do the same thing. In this way, if a user is logged in as non-root and types $ pear install Package the error message could be something like: $pear install Package Error: You don't have sufficient privileges to access pear install, use pear --local install Package to install a local copy in ~/.pear/PEAR/Package This would simplify docs, as a quickstart guide could be written, both for hosters (you too can allow people to install pear with no problem) and for non-hosters. This could probably actually be done without change to the PEAR installer if we also distribute a shell script for linux and a batch file for windows that would detect the current directory, check for a .pearrc, and if it isn't there, create it and populate it with values specified by the user, otherwise use it for the installation $ pearlocal install Package Create ~/.pearrc? Y [prompts similar to go-pear] Greg Pierre-Alain Joye wrote:

On Mon, 29 Sep 2003 14:40:34 +0200 "Tomas V.V.Cox" <cox@idecnet.com> wrote:

IMHO this is just a documentation problem. The pear installer was designed taking in mind this issue. One just need to create a config file for your user or app. For example:

This will install php classes at <somedir>, documentation at <somedir> and extensions at <somedir>, instead of the system wide paths.

IMHO too. That's one of the points I raised while talking about multiple installations on the same system. pierre