Re: Re: pyrus woes

On Mon, Jun 28, 2010 at 8:07 PM, Gregory Beaver <greg@chiaraquartet.net> wrote: > pyrus my-pear .:/home/user/commonpear > pyrus . install packagename > > Already does what you want. > > Or, you can skip the first step and pass in the directory for all calls: > > pyrus /path/to/project <anycommand> > > This is easily scripted per-project as well. It's still not all this obvious to me. Let's say I do the following: php pyrus.phar mypear /home/till/project1 php pyrus.phar mypear /home/till/project1/subproject cd /home/till/project1/subproject php pyrus.phar install HTTP_Request ... which of my pear "installs" is used? Also, if I do not use "mypear" at all - what is used in this case? $HOME ? Till > > Greg > > > > On Jun 28, 2010, at 11:59 AM, Evert Pot <evert@filemobile.com> wrote: > >>> >>> Also, I noticed that it'll create the .pear directory in $HOME. What >>> about putting it into $PWD instead, or at least letting people decide >>> this? It would be nice to have this per project, self-contained, etc.. >>> This would also imply that a local .pear/ directory is always read >>> first. >> >> I really like this. I think, in general, you would want specific versions and dependencies >> per-project, not per-system (or per-user). Having pear packages by default in a local directory, >> instead of a global one would be a great idea in my opinion. >> >> Evert >