Re: Re: pyrus woes

On Mon, Jun 28, 2010 at 12:59 PM, 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. This is how Pyrus works. Please read the documentation. The ~/.pear directory only tells Pyrus what the last-used local registry was, and what plugins you have installed for pyrus. Plugins are not regular packages, they modify the pyrus.phar commands and are tied to the system where they were installed. (PEAR2_Pyrus_Developer is a plugin). Each PACKAGE registry is localized in the directory you set with pyrus mypear ./vendor, the directory you tell pyrus to install packages in when it asked you initially, or the path you pass to each command pyrus ./vendor install PackageName. -- Brett Bieber