Re: Bundling Console_Getopt with the PEAR package

On Thu, Jul 03, 2003 at 03:29:14PM +0200, Pierre-Alain Joye wrote: > > Now imagine what happens if Console_Getopt is removed as a standalone > > package from PEAR... > > That's why Tomas asked it. The idea is to prevent such bad events. That > said, once we clearly announce that some weeks before do it, that should > not be a problem. > > The different packages will get time to update their docs and their > dependencies (in or out of pear.php.net). And the current release will > *always* be available. > > Being part of the "core", GetOpt will be available as well for everyone > who does not take care about deps using package definitions. > > So the question should be, what is the good time span to do not create a > mess once we merge the 2 packages? i.e. I do not think that should be > the case in the upcoming 4.3.3 but rather in a (if it'll exist) 4.4 or > 5.x. This still won't work well. We'll use the Horde case again. What happens if a user has an old version of PHP (say, 4.3.2) and a version of Horde that mentions Console_Getopt in the installation documentation? Upgrading PEAR would solve the problem, technically, but not before they run to the Horde mailing lists asking about the Console_Getopt package. There's no reason for the Console_Getopt package to be removed. Just install it by default, and everyone is happy. -- Jon Parise (jon@php.net) :: The PHP Project (http://www.php.net/)