> > building say apache module and cli at the same time with some extensions > > that are available in interactive mode only. With my proposed extension to > > PHP_EXTENSION the build becomes "smart" in that it links those extensions > > only with the cli, and not with the other api selected with the build. > > IMHO this is to smart after all as it might be smarter than the user :( > > 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. > 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. Anyway, I don't see a good reason why not to do it. Edin -- 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]
