Re: Re: Stable code with unstable dependancies.

Stefan Neufeind wrote:

What to do if a package v1.4 is stable and v2.0 is again marked as "beta" because of many api-changes? With an optional dependency you would install 2.0 but with a required dep you would install v1.4? This leads us again to the multi-version-packagesystem *g* There is some progress towards this in CVS.

If you just pass in a package name on the command-line, it will attempt to install the preferred state. In other words, if you use the new -a command-line switch, it will install a preferred-state or better package for each dependency. Of course, it doesn't resolve the problem of what to do with different major API versions. I think that there is no automated way to solve this, and individual packages should specify a different base install dir for new major version numbers, until PEAR 2.0 can introduce the channel idea and other major BC breaks. In other words, instead of using baseinstalldir="PhpDocumentor" I would use baseinstalldir="v2/PhpDocumentor" It will be very important to standardize what the directory should be named. 2.x would be fine too as in "2.x/PhpDocumentor" I'm just not sure every OS likes having a number as the first character of a pathname, which is why I thought v2 might make more sense. Regards, Greg