From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30800 invoked by uid 1002); 10 Jun 2003 03:02:15 -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 17985 invoked from network); 10 Jun 2003 03:02:15 -0000 Date: Mon, 9 Jun 2003 23:02:05 -0400 From: Donny Davies To: gentoo-dev@gentoo.org Message-ID: <20030610030204.GA31790@breccia.escarpment> Mail-Followup-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> <3EE4C2A5.9070600@brad-x.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <3EE4C2A5.9070600@brad-x.com> User-Agent: Mutt/1.5.4i X-Authentication-Info: Submitted using SMTP AUTH LOGIN at fep04-mail.bloor.is.net.cable.rogers.com from [24.112.125.236] using ID at Mon, 9 Jun 2003 23:02:14 -0400 Subject: Re: [gentoo-dev] apache.eclass proposed X-Archives-Salt: 7582f085-2589-4cb4-861b-606d2dfe4602 X-Archives-Hash: 1262a25c3738e244a2c5629f77215059 Ned Ludd wrote: >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 would strongly advise you to get your facts straight before rolling through here muttering something like that. This is not correct. I'm afraid you need to do some remedial reading on the situation. You may want to visit http://www.pathname.com/fhs/ where you can learn that there *IS* no standard for this. And as such, the location in which to install Apache and other web-related files, is simply nothing more the opinion of the person you're currently talking to. The current FHS version doesnt address this area. I havent looked at any of the work in progress for FHS 2.3 by the way; perhaps there's new developments there? If you want even more standards, then please open your config.layout file, distributed with the Apache source code, and well, take your pick from several more "standards". >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. There are other reasons to use this location, but none of them to do with FHS. :-) As for the apache2 USE flag; I made it so that the mod_php ebuild didnt have to *guess* at which API to build the DSO for. I've talked with Robin about this, and we'd both very much like to see it "go away". It's nasty. Robin H.Johnson wrote: >Having both installed simultaneously is a very messy business already, >as they both use /home/httpd, and contain binaries with identical names. They are configured to serve from the same DocumentRoot. I didnt want to introduce *another* docroot. They'll overwrite some icons from the other's install. I assume those who really, really want those default ASF icons from the other version, can figure out howto get them from the tarball. Same for the default introduction pages. Is this a big deal? What binaries are you talking about? I took pains to SLOT=2 Apache2, Im not aware of any binaries getting overwritten. As for the eclass, it's obviously a natural progression. I have not attempted to create one yet because I dont really have a great idea for what functions it should provide. The very basic ones proposed were simply not enough to convince me to add this yet. If they were I would have added one months ago. What other functions would be desired from an web-related eclass? I'm not *completely* and outright opposed to the stuff proposed, Im just saying it's weak, and well, it certainly isnt a sic "way to totally and easily manage the whole Apache config" as somebody else mentioned. Far from it. Further, Im not of the opinion that having a "bonifide" location in which to install these files on a Gentoo system (/home/httpd/{htdocs,cgi-bin} is a BAD idea, and having them just the way they are now at least provides this. Donny. -- gentoo-dev@gentoo.org mailing list