From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20739 invoked by uid 1002); 12 Jun 2003 00:13:01 -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 12168 invoked from network); 12 Jun 2003 00:13:01 -0000 Message-ID: <3EE7C58E.7020002@snerk.org> Date: Wed, 11 Jun 2003 20:13:02 -0400 From: Stewart Organization: Snerk World Enterprises User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030529 X-Accept-Language: en-us, en MIME-Version: 1.0 To: solar@gentoo.org Cc: gentoo-dev@gentoo.org References: <1055067141.13370.109.camel@simple> In-Reply-To: <1055067141.13370.109.camel@simple> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [gentoo-dev] apache.eclass proposed X-Archives-Salt: 6090093c-db41-4d77-8a5e-84d4ecb7ead0 X-Archives-Hash: 709171494e2cbc109fb220532fac51ed 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 Absolutely. I'm presently maintaining a couple net-www ebuilds and found it annoying that the default HTDOCS folder was assumed. I'd rather see a unified eclass file than a kludge in every ebuild. Most everything looks great, and I'd love to begin testing this. I've got three production and half a dozen test servers at my disposal with various combinations of Apache and Squid installed that I'd be able to toy with at the moment. -- Stewart Honsberger http://blackdeath.snerk.org/ "Capitalists, by nature, organize to protect themselves. -- Geeks, by nature, resist organizaion." -- gentoo-dev@gentoo.org mailing list