Re: Making local installations easier
| From: | Pierre-Alain Joye | Date: | Mon, 29 Sep 2003 15:52:28 +0000 |
| Subject: | Re: Making local installations easier | ||
| References: | 1 2 3 4 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-22168@lists.php.net to get a copy of this message | ||
On Mon, 29 Sep 2003 11:42:50 -0400
Greg Beaver <greg@chiaraquartet.net> wrote:
> 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.
I missed the point here, not that I do not like an alias. I'm wondering
how that will ease the write of a guide.
> $ pearlocal install Package
> Create ~/.pearrc? Y
> [prompts similar to go-pear]
I dot not like the idea of adding a pearlocal command, that sounds a bit
weird to me (do we have a pear remote?).
We may better to use ENV var and update accordingly pear.bat|sh to use
them.
pierre