Even with a menu-driven approach (e.g.: make menuconfig in the kernel)? My thought is that you'd still feed the end result through ./configure, but the app would make it somewhat easier for those who don't have a clue. It would also be possible to distribute "pre-packaged" configurations for common scenarios, thus removing the problem of what to distribute by default.
Cheers, Marco On Tue, 2003-06-24 at 10:51, Dan Kalowsky wrote: > I've proposed such solutions in the past, and only recently have come to > dislike the means (but not the idea). Mainly because the mechanism to do > such a configuration could lead to a longer configuration time then > compile time. > > > > On Tue, 24 Jun 2003, Marco Tabini wrote: > > > Why not disable all extensions by default and add a configuration > > utility that is launched before compilation--sort-of like the Linux > > kernel? > > >---------------------------------------------------------------< > Dan Kalowsky "I'll walk a thousand miles just > http://www.deadmime.org/~dank to slip this skin." > [EMAIL PROTECTED] - "Streets of Philadelphia", > [EMAIL PROTECTED] Bruce Springsteen -- Marco Tabini President Marco Tabini & Associates, Inc. 28 Bombay Avenue Toronto, ON M3H 1B7 Canada Phone: (416) 630-6202 Fax: (416) 630-5057 Web: http://www.tabini.ca -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
