> >The build process should be altered so that the standalone interpreter (cgi > >sapi) is always built so the traditional make && make install installs > >/usr/bin/php no matter what sapi module was chosen. > > I'm +1 on this, even though I think that PHP isn't very well suited > for shell jobs in comparison to Bash or Perl.
I don't know Perl, but I cannot see what's the advantage of using bash (except for the infamous exit() function) over PHP. If there are any maybe we can do something about it. The same goes for Perl. > Always building the CGI version would also help the PEAR command > line installer a lot since it currently needs a PHP binary to be > executed. Yes, I had that in mind. We should get /usr/bin/php on as many machines as possible. This message from Stig S. Bakken summarises nicely what I'm trying to say: http://marc.theaimsgroup.com/?l=php-dev&m=100313140811956&w=2 -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
