> 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 feel an explicit --enable-cli should do that but 
regardless the current method has been documented.  The 
distinction can be seen in this unxmled excerpt:

 If a module SAPI is chosen during configure, such as apxs, 
 or the --disable-cgi option is used, the CLI is copied to
 {PREFIX}/bin/php during make install otherwise the CGI 
 is placed there. 

Because CLI is a SAPI so I guess only module (web servers) 
count.  Anyway please have a look at:

http://cvs.php.net/diff.php/phpdoc/en/features/commandline.xml?r1=1.12&r2=1.13

And make sure this is written correctly.  If so, information
from it will also live in install.commandline.  Btw, it sure
is weird writing examples when cgi and cli have the same 
name and get installed at the location.  I didn't change 
those much.  I also didn't add the history of what these 
files were called in 4.2.x as I'm not fully sure how it all 
worked back then *hint* *hint*.

Regards,
Philip Olson


-- 
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to