On Wed, 18 Dec 2002, Shane Caraveo wrote:
> Edin Kadribasic wrote:
[snip]
> > I really don't understand why insist on cgi being installed on "make
> > install" to ${PREFIX}/bin? The solution outlined by Andrei and Derick is
> > much better IMHO because it will alert users of the issue and because
> > installing a cgi into a webserver requires manual action anyway.
>
> It's realy very logical. It leaves the default installation the way
> most people will expect it to behave, which is as it has been for years
> now. Having the options allow people to modify that behaviour to the
> way they want it to work. It's very flexable for all interests.
This seems to be matter of personal opinion.
I happen to belive that having cli in /usr/bin/php is a real improvement
over having cgi there. For command line scripts cli is
(nearly) a drop-in replacement for cgi. I am not aware of webserver
installs that use cgi in that location.
My great wish was to have the same freedom perl programmers have in
distributing scripts with #!/usr/bin/perl shebang line. Scripts that you
could nearly count on being executable on the target host. And scripts
that would always work, no matter from which context they were called.
Edin
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, visit: http://www.php.net/unsub.php
