Re: PEAR2 in CVS

Greg Beaver wrote:

- [not yet implemented] PEAR will be tightly linked to include_path, so that installation will assume include_path represents a chain of PEAR repositories and it will search for a "parent" PEAR repository when installing a package. This means, for instance, that if Console_Getopt is installed in the "parent" PEAR repository, it will satisfy dependencies when installing into the local PEAR repository. The risk, of course, in this case is that the dependency is 1-way: Console_Getopt can be uninstalled from the parent repository and it will break the child repository, so it will be possible to disable this by passing in an include_path value to use or php.ini to use

this one will be tricky to get right and even trickier to communicate to users. as such it should definitely be off by default. people should explicitly have to enable it. anyways cool stuff. as i noted on my email to pear-dev about the Doctrine base class, we should provide an sample autoload implementation. where should it be? should be try to separate any new base classes in PEAR from the installer? should we even start thinking about renaming the installer so that we reduce some of the confusion over what PEAR is (installer, base class, a repository)? regards, Lukas