> > I have to disagree with you guys here. We are, after all, past RC1 at
this
> > point and doing a major surgery on php and its build and test systems is
> > irresponsible.
>
> A very big point, I totally agree with you on this. This is not an option
> after all.
>
> > I hate to say it, but there were plenty of opportunities to
> > bring up the issues with CLI in the past several months.
> >
> > I could go the long way and repeat the motivatiom behind the creation of
CLI
> > at this point, but instead I would like to recommend that we take
> > evolutionary approach. First make CLI a CGI without all the CGI garbage.
> > Always build it with PHP. (this is where we are now). The next step is
> > moving PHP in the direction of general purpose scripting language.
>
> And what if we disable the CLI by default for 4.2.0 and make a switch
> --enable-cli to enable building of the CLI. This makes it more clear that
> it's still experimental. In 4.3.0 we simply change the default to always
> build the CLI.
I still think that people need to adjust to some major changes CLI brings
(not chdiring into the scripts directory, etc.)...
But... if you insist.
Disabling it is not good due to the test suite, etc. Instead:
1. Mark it experimental.
2. Change make install not to install it.
3. Change make install on cgi to install it in {BINDIR}/php as it used to.
In that way people will not notice its presence, and even if they do its
marked experimental. The changes we need to make to the build system are
minimal.
Edin
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, visit: http://www.php.net/unsub.php
