Re: Looking towards PEAR2?

Joe Stump wrote: > Per our amazingly shortsighted CS I thought of a serious problem having > to do with the "Major new revisions must be named PackageX where X is > the new major version". What happens when PEAR moves to the next major > version? Will it ship on PHP as PEAR2? Will I then have /usr/bin/pear > and /usr/bin/pear2? Will there be two different directories containing > PEAR modules (one for ones installed via PEAR 1.x and one for ones > installed via PEAR 2.x)? > > Will PHP ship with both and then, at compile time, you'll have to > choose which one to install? Per the CS rules the package will HAVE to > be named PEAR2. Does this mean I'll have to change all of my > PEAR::isError()'s to PEAR2::isError()? > > Wow, that'll suck big time. I hate to burst your bubble Joe, but if and when PEAR2 were to come out, it will most definitely NOT include the PEAR class. I mean, honestly, what makes you think PEAR_Error has any relevance in PHP 5+? If PEAR2 comes out, it will be a complete rewrite, totally incompatible with PEAR, so I don't think you have anything to worry about. As for the CS being shortsighted, I have yet to see any problems with the package naming scheme except that every once and a while someone comes along and posts FUD about it :). What has actually happened is the stability of PEAR packages has skyrocketed, and folks are no longer cavalierly breaking BC, nor are they jumping to "stable" far too early for anyone's good. Greg