Re: CLI Sapi automatic build

From: Date: Mon, 14 Jan 2002 12:30:19 +0000
Subject: Re: CLI Sapi automatic build
References: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17  Groups: php.dev 
Request: Send a blank email to php-dev+get-77047@lists.php.net to get a copy of this message 
Edin Kadribasic wrote:


i'm alread expecting bug reports regarding "my apache module doesn't have
extension xyz although i configured it ..."



Come on, give our users some credit :) I think that concept of extension's
that work only with cli shouldn't be too difficult to grasp.



have you ever spent some time reading the bug reports :(



i'd prefer to do the checks my way, if one wants a customized
CLI then he/she should explicitly configure for CLI IMHO
i already build different configured executables for CGI and
for command line use with the current CGI sapi



This defeats the whole purpose of having any changes to the build. The whole
reason for doing this was to enable building a server api and cli binaries
at the same time. If I needed to configure and make php twice, I could just
as well leave the build as it is.



if you want PHPs that differ in functionality, then yes, that's

what you have to do: reconfigure and recompile

wasn't the reason for having a CLI build in parallel
with the requested SAPI to use it for bootsraping and
things? or did i get something wrong here? might well
be so, haven't paid as much attention to the lists
as i should have for the last three weeks or so ... :(





Anyway, I don't see a good reason why not to do it.


just go ahead, do not let me disturb you doing a great job,
just don't forget to treat readline and ncurses the same
way you do with pcntl

PS: i know who to assing the bug reports to ;)

-- 
Hartmut Holzgraefe  hartmut@six.de  http://www.six.de 
+49-711-99091-77

Thread (21 messages)

« previous php.dev (#77047) next »