Re: PEAR CVS version

Hi Pierre, The latest commit from Andrei was the BC breaker. Although merging GetOpt into the PEAR core makes sense on a certain level, there is only one problem with it. If we include the new GetOpt in the next release of PEAR, it will break PECL_Gen and System_Procwatch, as well as any user-land projects that use GetOpt. In other words, we would be forced to release PEAR2 - this not good thing, methinks. The only sensible solution is to release Console_Getopt2 - this fits in with the BC guidelines, and then PEAR can depend on it, and other packages can take their time to update their dependencies. What do you think Andrei? Greg P.S. the thread was on pear-general to halt the impending flood of "go-pear isn't working with some error unable to make :/tmp4Guf error" messages :) Pierre-Alain Joye wrote:

On Mon, 8 Dec 2003 13:16:36 +0100 "Klaus Guenther" <klaus@capitalfocus.org> wrote:

From: "Arnaud Limbourg" <arnaud.limbourg.prestataire@cegetel.fr>

Why the dependency on console_getopt 2.0 when it does not exists ?

Because console_getopt 1.1 release (now retracted) broke almost everything. So, Greg renamed it 2.0 and made created a package.xml to fix all the problems. See http://marc.theaimsgroup.com/?l=pear-general&m=107074961314512&w=2 for details.

I missed this thread (why in the world has it been on pear-general???). Greg, what's the status with this problem? Is the latest commit from Andrei related to this exact problem? Anyway, this dep is wrong. If the head GetOpt is the fixed and stable sources, we should ask for a new release and then "fix" PEAR as required. However I would like to merge GetOpt in the PEAR package itself (and give to Andrei the karma if he still does not have it) to avoid such problems and ease our lifes (and minimize heartbreaks...). pierre