From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6111 invoked by uid 1002); 9 Jun 2003 03:08:03 -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 27867 invoked from network); 9 Jun 2003 03:08:03 -0000 From: Ned Ludd Reply-To: solar@gentoo.org To: gentoo-dev@gentoo.org In-Reply-To: <200306082150.52849.pauldv@gentoo.org> References: <1055067141.13370.109.camel@simple> <20030608194535.GA548@cherenkov.orbis-terrarum.net> <200306082150.52849.pauldv@gentoo.org> Content-Type: text/plain Organization: Gentoo Linux (Hardened) Message-Id: <1055128068.8987.185.camel@simple> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2- Date: 08 Jun 2003 23:07:49 -0400 Content-Transfer-Encoding: 7bit Subject: Re: [gentoo-dev] apache.eclass proposed X-Archives-Salt: 9b54047e-48ec-4efd-98fc-5b73bc10c8c0 X-Archives-Hash: 9e2c86830838650920276f1fd39d0a96 First I'd like to say sorry to the ml this should of been called an apache.eclass draft. On Sun, 2003-06-08 at 15:50, Paul de Vrieze wrote: > On Sunday 08 June 2003 21:45, Robin H.Johnson wrote: > > On Sun, Jun 08, 2003 at 06:12:21AM -0400, Ned Ludd wrote: > > > After writing a net-www/ ebuild it seemed apparent to me that we are > > > going to need an apache.eclass. A quick find in portage reveals quite a > > > few independent ebuilds all needing the basic functionality that could > > > be provided by an apache.eclass > > > > I agree that having this would be worthwhile, however it has been said > > higher up before that /home/httpd/htdocs would be where things were > > installed. > > What about the users that are changing there default DocumentRoot's? Are we to ignore that completly and install to /home/httpd/htdocs anyway? > > A few problems with this. > > 1. What about people that have both installed? I actually have an open > > bug for mod_php about this, and I'm trying to decide on a workable > > solution. Presently I'm leaning towards an enviroment variable > > 'FORCE_APACHE=1|2' that overrides any detection routines, for the > > special case of people that have both. > Such and enviroment variable would make things quite less complex. > This is what the apache2 use variable is supposed to do. At least, as far as I > know. It does not behave this way for me, try USE=-apache2 with KEYWORDS=~x86 while wanting to keep an apache2 from getting installed. Aparently the apache2 use flag was introduced to break the tie if both apache 1 and apache 2 were installed but very few people are using it correctly though, thus the need for these things to be addressed by an eclass vrs everybodys the ebuilds themselfs. -- Ned Ludd Gentoo Linux (Hardened) -- gentoo-dev@gentoo.org mailing list