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)?

As others have explained you would end up with /usr/bin/pear/PEAR2.php living happily side by side with /usr/bin/pear/PEAR.php What you call shortsighted solves the technical problems of: - being able to run scripts with both major versions - being able to install both major versions Solves the social problems of: - tending towards constantly throwing out old stuff for academic reasons - makes people think twice before marking things stable prematurely

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 am sure you will be able to come up with a short search replace call in your favorite IDE or shell scripting language if such a change is necessary. In short: the solution we have is actually very good. it goes way beyond what namespaces would ever be able to offer us. regards, Lukas