Re: AW: [PEAR-DEV] BC breakage results

Hi! Stefan Neufeind wrote:

I think that slot-based solution is better than mandatory installation of different versions into different directories. Thus we let users decide what to do with the packages. One can install the package into slot 1, test it, then upgrade the package in the main slot. Or one can install older version of the package to the slot 1 and install the package that depends on it. More power to the users.

Partially agreed. But where from do scripts know which slots they should use? I guess your solution isn't pointing at having several major versions installed at the same time and even use libs in one application where one requires 1.x and the other 2.x, right?

Well, I thought that this solution is for having several versions of the *same* package installed at once, Foo and Foo2 should probably be considered different packages. User's scripts should explicitly require scripts from the needed slot: require_once '1/Foo.php'; PEAR packages will have their include statements mangled by the PEAR installer. I don't think that it will be intended for the production servers, though. But it is easier than juggle separate PEAR installations on development ones.