Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 19709 invoked by uid 6000); 23 Jun 1999 03:46:48 -0000 Received: (qmail 19588 invoked from network); 23 Jun 1999 03:46:42 -0000 Received: from devsys.jagunet.com (206.156.208.6) by taz.hyperreal.org with SMTP; 23 Jun 1999 03:46:42 -0000 Received: (from jim@localhost) by devsys.jaguNET.com (8.9.3/jag-2.6) id XAA17327 for new-httpd@apache.org; Tue, 22 Jun 1999 23:46:37 -0400 (EDT) From: Jim Jagielski Message-Id: <199906230346.XAA17327@devsys.jaguNET.com> Subject: Re: Head's up To: new-httpd@apache.org Date: Tue, 22 Jun 1999 23:46:37 -0400 (EDT) In-Reply-To: from "Greg Stein" at Jun 22, 99 08:28:43 pm X-Mailer: ELM [version 2.4 PL25] Content-Type: text Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org Greg Stein wrote: > > On Tue, 22 Jun 1999, Jim Jagielski wrote: > > Just a head's up. I'm working on some improvements to the > > Configure process and how it implements modules. Basically, > > I'm looking at a technique that will allow almost anything to > > be considered a "module" (such as the expat lib, for example). > > Mainly it's for 2.0/apr but could be useful for 1.3.7/1.4.0 > > (although I wouldn't hold it for that). No matter what, it'll > > be such that it extends what we have, not replaces it... > > Well... if it fits in with autoconf and can handle all the functionality > of the old, then I'd say we torch the old. Why have two ways to do the > same thing? Just adds to the overall complexity. > > Of course, we'd like third-party module to not require many changes, but > I'll happily monkey with the expat-lite directory to conform to new stuff > if we can simplify the configure/build process. > The idea is to have NO changes required. The rub is that Configure "assumes" that modules are setup as modules/name/whatever.o and only that deep. For 2.0 it would be nice to have modules/mpm/prefork/libmpm_prefork.a and similar things. We could even make it generic enough so that AddModule could be use to add regex or expat or anything else. This sort of internal monkeying around may not be suited for autoconf... I have no idea how autoconf can do the kind of Module manipulation (including the run-time stuff) we're currently doing. -- =========================================================================== Jim Jagielski ||| jim@jaguNET.com ||| http://www.jaguNET.com/ "That's no ordinary rabbit... that's the most foul, cruel and bad-tempered rodent you ever laid eyes on"