Received: (from majordom@localhost) by hyperreal.org (8.8.5/8.8.5) id LAA06469; Wed, 13 Aug 1997 11:28:34 -0700 (PDT) Received: from devsys.jaguNET.com (devsys.jaguNET.com [206.156.208.6]) by hyperreal.org (8.8.5/8.8.5) with ESMTP id LAA06462 for ; Wed, 13 Aug 1997 11:28:30 -0700 (PDT) Received: (from jim@localhost) by devsys.jaguNET.com (8.8.7/jag-2.4) id OAA19941 for new-httpd@apache.org; Wed, 13 Aug 1997 14:28:25 -0400 (EDT) From: Jim Jagielski Message-Id: <199708131828.OAA19941@devsys.jaguNET.com> Subject: Re: apachen and modules/extra To: new-httpd@apache.org Date: Wed, 13 Aug 1997 14:28:25 -0400 (EDT) In-Reply-To: from "Alexei Kosut" at Aug 13, 97 11:07:39 am X-Mailer: ELM [version 2.4 PL25] Content-Type: text Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org Alexei Kosut wrote: > > On Wed, 13 Aug 1997, Jim Jagielski wrote: > > > I'm wondering... Would it be better to rename that directory as > > something like modules/need_makefile or something like that? > > My concern is that whatever modules are placed there, Configure > > will create it's own Makefile. If the module has it's own, then > > Configure will over-write it. By renaming the directory, it may > > be a bit more clear, esp for those who don't read the docs too > > well. > > Nah. I think modules/extra is good. Any module that does come with a > Makefile will come in a directory with directions saying "move this > directory into src/modules". If they don't follow that, it probably won't > work anyway. > As long as the fact that any Makefile in modules/extra is overwritten is documented... -- ==================================================================== Jim Jagielski | jaguNET Access Services jim@jaguNET.com | http://www.jaguNET.com/ "Look at me! I'm wearing a cardboard belt!"