So every tutorial and documentation on this would have to say this right? "Ask your sysadmin what the CGI and CLI versions of your PHP are called, they could be anything as there is no standard. For the purpose of this (tutorial|documentation), we'll call CLI php-cli and CGI php-cgi."
Same goes for all cgi scripts, they'll work some places but not others... And various RPM's would have different naming schemes depending on the maintainers preference. Regards, Philip On Wed, 18 Dec 2002, Andrei Zmievski wrote: > On Wed, 18 Dec 2002, Andi Gutmans wrote: > > I doubt this will happen fast enough. We should just release the way we > > released 4.2.x, which as far as I know was php for CGI and php-cli for CLI > > or am I a bit behind things? :) > > Derick and I hashed it out on IRC and we have a proposal: > > We should keep 4.2.x behavior with some modifications. CLI and CGI > should always be built unless disabled, and the executables should go > into sapi/cli/php and sapi/cgi/php, respectively. In addition, 'install' > target should be modified to detect whether the user is trying to > install either one of these SAPIs, output a warning message regarding > the potential naming problem, and stop. Let the user install CLI and CGI > manually, basically. > > I really hope we can come to an agreement on this. > > -Andrei http://www.gravitonic.com/ > * Quantum Mechanics: The Dreams of Which Stuff is Made. * > > -- > PHP Development Mailing List <http://www.php.net/> > To unsubscribe, visit: http://www.php.net/unsub.php > -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
