From owner-cvs-ports Sun Sep 24 17:15:04 1995 Return-Path: owner-cvs-ports Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA23360 for cvs-ports-outgoing; Sun, 24 Sep 1995 17:15:04 -0700 Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id RAA23344 ; Sun, 24 Sep 1995 17:14:57 -0700 Received: from localhost (localhost [127.0.0.1]) by precipice.shockwave.com (8.6.12/8.6.12) with SMTP id RAA03399; Sun, 24 Sep 1995 17:13:01 -0700 Message-Id: <199509250013.RAA03399@precipice.shockwave.com> To: John Fieber cc: CVS-commiters@freefall.freebsd.org, cvs-ports@freefall.freebsd.org Subject: Re: cvs commit: ports/net/apache/scripts configure In-reply-to: Your message of "Sun, 24 Sep 1995 18:28:45 CDT." Date: Sun, 24 Sep 1995 17:12:57 -0700 From: Paul Traina Sender: owner-cvs-ports@FreeBSD.org Precedence: bulk From: John Fieber Subject: Re: cvs commit: ports/net/apache/scripts configure On Sat, 23 Sep 1995, Paul Traina wrote: > Log: > Upgrade apache to 0.8.14, completely restructure port, and list myself as > maintainer. Gee... And I just spent a bunch of time working on this this! Well, I do have a couple suggestions though. 1) Can we install the binary as /usr/local/libexec/httpd? Agreed, 100%. 2) Currently DocumentRoot is $PREFIX/www while ServerRoot is $PREFIX/www/server. This is a Bad Thing since it makes all the server configuration files freely available to anybody poking around with a WWW browser. I would recommend making ServerRoot $PREFIX/www and DocumentRoot $PREFIX/www/data (or htdocs, or documents, or whatever). Yes, I changed mine to $PREFIX/www/data (the document root), and left $PREFIX/www/server alone. This makes it a peer with $PREFIX/www/icons. I have no objection to making this change, and will do so if you don't think it will hose up too many folks. 3) Which brings up another point. httpd.conf, access.conf and srm.conf all need to be altered in the event of $PREFIX being something other than /usr/local. Its easy enough to do when installing a port, but I'm not aware of the mechanism used for packages... Neither am I, however I think most people don't dare install packages in alternate locations anyway because almost every package is laden with problems like this. I'm open for suggestions. Related, While mucking around with those file, its pretty easy to insert a correct hostname for ServerAdmin instead of "localhost". Agreed, but compile host != run host, I'd rather not make a bad guess. -john == jfieber@indiana.edu =========================================== == http://fieber-john.campusview.indiana.edu/~jfieber ============