Re: [PATCH] CLI and CGI defaults

On Tue, 24 Dec 2002, Andrei Zmievski wrote: AZ>>> On Mon, 23 Dec 2002, Melvyn Sopacua wrote: AZ>>> > Hi, AZ>>> > AZ>>> > the current behavior of cli/cgi defaults, is not really intuitive, allthough AZ>>> > correctly mentioned in the NEWS entry. AZ>>> > AZ>>> > Attached is a very simple patch, that will resolve that issue. AZ>>> > AZ>>> > Specifically: AZ>>> > if you specify --enable-cli and don't specify --enable-cgi, then CLI will AZ>>> > be installed and built. The current behavior, is that CGI will be installed and built, which will AZ>>> > (and already has) lead to confusion. AZ>>> AZ>>> Isn't the current behavior to always build CLI unless --disable-cli is AZ>>> specified but not install it unless install-cli target is used? Yes, unless --disable-cgi is given, then make install will install CLI. Quoting from NEWS: "If you don't specify building any other SAPI "make install" will install the CGI SAPI binary in {PREFIX}/bin/php." so, reading that *only* you'd think --enable-cli will install CLI. It's corrected in the next line: "If you want to install CLI SAPI in that location use "make install-cli" after "make install" or add --disable-cgi to your configure options." But --enable-cli is now a useless switch, because: * if you don't specify it, cli is built * if you specify it, cli is built * if you don't specify it, cli is not installed * if you specify it, cli is not installed Only --disable-cgi (--enable-cli still makes no difference) will install cli on make install. See: http://bugs.php.net/bug.php?id=21145 for an example of the confusion. -- With kind regards, Melvyn Sopacua <?php include("not_reflecting_employers_views.txt"); ?>