Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 14218 invoked by uid 6000); 2 Dec 1997 16:09:34 -0000 Received: (qmail 14200 invoked from network); 2 Dec 1997 16:09:23 -0000 Received: from gate-isdn.ukweb.com (194.152.65.149) by taz.hyperreal.org with SMTP; 2 Dec 1997 16:09:23 -0000 Received: from ecstasy.localnet [192.168.2.4] by gate-isdn.ukweb.com with smtp (Exim 1.73 #1) id 0xcusx-0002yY-00; Tue, 2 Dec 1997 16:09:19 +0000 Date: Tue, 2 Dec 1997 16:09:11 +0000 (GMT) From: Paul Sutton To: new-httpd@apache.org Subject: Re: [PATCH] Configure to say how to make Configuration In-Reply-To: <009BE202C710E265.7A01@PROCESS.COM> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org On Mon, 1 Dec 1997, Rodent of Unusual Size wrote: > >From the fingers of Martin Kraemer flowed the following: > >Yes, that's why I brought the dbm/db question to the table: I have > >several OS's here which don't come with a db library. OTOH I assume > >recent *bsd systems don't use dbm any longer. The "canonical set" > >could therefore only be empty. > > For things like DB support, true. But other modules don't have any > dependencies upon the OS - such as the proxy, mod_setenvif, > mod_mime, mod_alias, mod_acces, mod_rewrite, ... Those can be > included in the canonical set. I agree. There are some (minor) differences caused by particular OS'es. But the majority of modules can be included on any build - rewrite, proxy, setenvif, etc. We should decide which modules are going into the default binary builds, then make all builds include those modules. And the Configuration file should be updated to build the same set of modules, by default. People can easily comment in or out the AddModule lines as they need, but at least they are starting with something consistent with the binary kits. //pcs