Re: always building cgi...

[Sascha Schumann <sascha@schumann.cx>] > > Okay, what about making libphp4.la contain everything but libsapi.la, > > and make a new final target including libsapi.la called > > libphp4_xxx.la, where xxx is the sapi module used. > > > > With some more minor restructuring, we can then let people build _all_ > > sapi modules in one go if they like. > > [my internet link died yesterday and I forgot to resend this] > > Without careful consideration, I would not say that it would > require only minor restructuring. If we would implement that > change, it would have a direct effect upon the installation > procedure of PHP. That is not a problem with online > documentation, but what about printed manuals and the dozens > of books on PHP? I'd be very hesitant to change anything > here which would render those descriptions invalid. > > On the implementation side, I'm not convinced of the > usefulness of such a change. The way libphp4.la is built > directly depends upon the chosen SAPI module (thread-safety, > shared/static). As of today, there are only a few possible > combinations. From day-to-day experience, I have yet to see > an installation where web-servers run parallelly (and which > use PHP/require the same build options). It would probably only be useful to distribution builders. However, the point is having the CGI and something else at the same time. It seems this is leading us towards a 4.1 release. - Stig -- Stig Sæther Bakken <ssb@fast.no> Fast Search & Transfer ASA, Trondheim, Norway