Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 27449 invoked by uid 6000); 2 Dec 1998 08:20:15 -0000 Received: (qmail 27442 invoked from network); 2 Dec 1998 08:20:14 -0000 Received: from kurgan.lyra.org (root@208.192.43.9) by taz.hyperreal.org with SMTP; 2 Dec 1998 08:20:14 -0000 Received: from kurgan.lyra.org (localhost [127.0.0.1]) by kurgan.lyra.org (8.8.5/8.8.5) with SMTP id AAA12234 for ; Wed, 2 Dec 1998 00:17:28 -0800 Message-ID: <3664F796.19500F4B@lyra.org> Date: Wed, 02 Dec 1998 00:17:27 -0800 From: Greg Stein X-Mailer: Mozilla 3.01 (X11; I; Linux 2.0.28 i586) MIME-Version: 1.0 To: new-httpd@apache.org Subject: possible configuration idea Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org I'm going to stay out of this debate :-), but I've got a small idea to provide... One of the issues that has come up quite often is the portability of the different solutions, and how to ensure the portability. Problems creep up with shell features that can be used, additional support tools and commands that are available, etc. An approach that the MudOS LPmud driver took was to compile and build its own tool as part of the configuration process. The C code used *very* limited headers, used only the most basic library functions, and stuck to classic K&R. That tool was then used to assist the rest of the configuration process. A similar approach could be used by Apache for its configuration/build process to help with its portability. Cheers, -g -- Greg Stein, http://www.lyra.org/