Re: Bundling Console_Getopt with the PEAR package
| From: | Pierre-Alain Joye | Date: | Thu, 03 Jul 2003 13:29:14 +0000 |
| Subject: | Re: Bundling Console_Getopt with the PEAR package | ||
| References: | 1 2 3 4 5 6 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-17957@lists.php.net to get a copy of this message | ||
On Thu, 3 Jul 2003 13:46:02 +0200
Jan Schneider <jan@horde.org> wrote:
> It is. To give you a real world example: You can't believe how many
> Horde users we had that tried to install HTML_Select as written in
> Horde's install instructions. First they didn't find this package at
> all because it was simply removed from PEAR. Then they wondered why
> nothing worked because HTML_Select has become a completely different
> package. Congratulation!
I missed the select issues, then I cannot argue here :)
> 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.
hth
pierre