Re: not-yet-draft RFC on the new versioning standards for PEAR2 (needs PEAR Group sponsor to be official)

Brett Bieber wrote: > On Wed, Jan 6, 2010 at 11:35 PM, Michael Gauthier <mike@silverorange.com> wrote: > >> On Tue, 2009-12-29 at 14:11 -0600, Brett Bieber wrote: >> >>> I've added myself as a sponsor to this RFC and marked it as a draft. >>> >>> If anyone has any remaining comments on this proposal, please send them now. >>> >>> >>> http://wiki.php.net/pear/rfc/pear2_versioning_standard_revision >>> >>> >> I had a bunch of feedback prepared for this RFC but then today on IRC, >> Helgi, Brett and I uncovered a larger problem -- that of parallel >> installability. >> >> Here's the problem: >> >> * Package-A depends on the API of HTTP_Request 1.x >> * Package-B depends on the API of HTTP_Request 2.x >> * User Alice wants to use both Package A and Package B in her >> application. Hi, Let's not forget that it is impossible to use 2 versions of the same package because they will have the same class names. No amount of path finagling can fix this, and it is an inherent problem. I also tend to think that this scenario is exceedingly uncommon (using 2 versions of the same package in the same PHP process). The main thing is that per-request, we should have one version of a package in use at a time. However, if the question is regarding 2 independent applications, then the solution is simple with Pyrus: create 2 separate installations, and use my_pear_path to utilize dependencies from the main install so that we only install HTTP_Request 2 in that install, and use include_path set to the same value. Greg