Received: by taz.hyperreal.com (8.6.12/8.6.5) id KAA07805; Tue, 2 Jul 1996 10:32:38 -0700 Received: from creche.cygnus.com by taz.hyperreal.com (8.6.12/8.6.5) with ESMTP id KAA07785; Tue, 2 Jul 1996 10:32:29 -0700 Received: (from tromey@localhost) by creche.cygnus.com (8.6.12/8.6.9) id LAA00375; Tue, 2 Jul 1996 11:33:03 -0600 Date: Tue, 2 Jul 1996 11:33:03 -0600 Message-Id: <199607021733.LAA00375@creche.cygnus.com> From: Tom Tromey To: new-httpd@hyperreal.com Subject: Re: support dir In-Reply-To: <199607020030.UAA01116@luers.qosina.com> References: <199607020030.UAA01116@luers.qosina.com> X-Zippy: Now I understand the meaning of ``THE MOD SQUAD''! X-Attribution: Tom Sender: owner-new-httpd@apache.org Precedence: bulk Reply-To: new-httpd@hyperreal.com >>>>> "Aram" == Aram Mirzadeh writes: >> Alexei Kosut said: >> >> I think that with autoconf, the "end user" should be able to do >> >> 1) configure >> 2) make >> 3) make install >> 4) run Apache >> >> make install would install the binary itself, along with the support >> tools, and properly tweaked config files into /usr/local/etc/apache or >> a like directory specified in configuration. This is pretty much exactly what our autoconfiscation does, except there is actually a separate "install-apache" script that sets up a simple Apache installation. We made this separate since only new users will want to run this script. Aram> Can autoconf do dynamic updating of a location? So if they want Aram> to install it in /usr/local/www they can do it? Absolutely. Just pass --prefix=/usr/local/www to configure. This is even conveniently documented. Tom -- tromey@cygnus.com Member, League for Programming Freedom