public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Stewart <bdlists@snerk.org>
To: solar@gentoo.org
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] apache.eclass proposed
Date: Wed, 11 Jun 2003 20:13:02 -0400	[thread overview]
Message-ID: <3EE7C58E.7020002@snerk.org> (raw)
In-Reply-To: <1055067141.13370.109.camel@simple>

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


  parent reply	other threads:[~2003-06-12  0:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-08 10:12 [gentoo-dev] apache.eclass proposed Ned Ludd
2003-06-08 19:45 ` Robin H.Johnson
2003-06-08 19:50   ` Paul de Vrieze
2003-06-09  3:07     ` Ned Ludd
2003-06-09  6:01       ` Robin H.Johnson
2003-06-09 17:23         ` Brad Laue
2003-06-10  3:02           ` Donny Davies
2003-06-10  5:43             ` Robin H.Johnson
2003-06-12  0:13 ` Stewart [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-06-08 14:32 Joshua Brindle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3EE7C58E.7020002@snerk.org \
    --to=bdlists@snerk.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=solar@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox