From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19341 invoked by uid 1002); 9 Jun 2003 17:23:31 -0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 17937 invoked from network); 9 Jun 2003 17:23:31 -0000 Message-ID: <3EE4C2A5.9070600@brad-x.com> Date: Mon, 09 Jun 2003 13:23:49 -0400 From: Brad Laue User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030430 X-Accept-Language: en-us, en MIME-Version: 1.0 To: gentoo-dev@gentoo.org References: <1055067141.13370.109.camel@simple> <20030608194535.GA548@cherenkov.orbis-terrarum.net> <200306082150.52849.pauldv@gentoo.org> <1055128068.8987.185.camel@simple> <20030609060131.GA2683@cherenkov.orbis-terrarum.net> In-Reply-To: <20030609060131.GA2683@cherenkov.orbis-terrarum.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [gentoo-dev] apache.eclass proposed X-Archives-Salt: bd873176-4e57-4b0a-b27c-0dd8bad02fdf X-Archives-Hash: aa7c0d1a19e7501556101a9913099172 Robin H.Johnson wrote: > I believe that would be a better solution than looking for the > DocumentRoot they have set. As an example, I run a couple of webservers > at work. Their DocumentRoot is /var/www, which is a read-only NFS mount. The means by which the DocumentRoot is found is actually pretty elegant and the functionality of that can easily be placed in an eclass. I'd consider this a big plus in terms of usability. As you're pointing out, /var/www is the FHS compliant place to put the documentroot anyway, so I'm not sure why we're being like RedHat in this respect. I don't think we should remove this. If there are ebuilds that don't comply with this method of finding out where the documentroot is, they can be fixed all the more easily using an eclass. > One further thing with the DocumentRoot issue. Say I have two systems > that share binary packages, but they have different DocumentRoot > settings. I create the binary tbz2 on the first system, and it packages > everything up with the first path, say /home/httpd/htdocs. Then I want > to also install on the second system, which has a DocumentRoot of > /var/www. The files would still be installed to /home/httpd/htdocs, > defeating the purpose of your check for the DocumentRoot setting. Is pkg_preinst observed when emerging a .tbz2 package? This would be another thing to change about the ebuilds in question. At the very least, why don't we make the httpd user's home directory /var/www? Alas, if we did so we would still require detection routines for currently installed systems. Brad -- // -- http://www.BRAD-X.com/ -- // -- gentoo-dev@gentoo.org mailing list