Andrei already decided, that --enable-cli should not change it's
behavior for 4.3, allthough I think it's intuitive for --enable-cli to
disable CGI if --enable-cgi was not given, I don't have a problem with
it, as long as the NEWS entry is correct and Philip documents it
correctly :)
I also
On Mon, 23 Dec 2002, Melvyn Sopacua wrote:
Hi,
the current behavior of cli/cgi defaults, is not really intuitive, allthough
correctly mentioned in the NEWS entry.
Attached is a very simple patch, that will resolve that issue.
Specifically:
if you specify --enable-cli and don't specify
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
correctly mentioned in the NEWS entry.
AZ
AZ Attached is a very simple patch, that will resolve that issue.
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
On Tue, 24 Dec 2002, Shane Caraveo wrote:
SC But --enable-cli is now a useless switch, because:
SC * if you don't specify it, cli is built
SC * if you specify it, cli is built
SC * if you don't specify it, cli is not installed
SC * if you specify it, cli is not installed
SC
SC Only
Hi,
the current behavior of cli/cgi defaults, is not really intuitive, allthough correctly
mentioned in the NEWS entry.
Attached is a very simple patch, that will resolve that issue.
Specifically:
if you specify --enable-cli and don't specify --enable-cgi, then CLI will be installed
and
