public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ned Ludd <solar@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] apache.eclass proposed
Date: 08 Jun 2003 23:07:49 -0400	[thread overview]
Message-ID: <1055128068.8987.185.camel@simple> (raw)
In-Reply-To: <200306082150.52849.pauldv@gentoo.org>

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 <solar@gentoo.org>
Gentoo Linux (Hardened)


--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-06-09  3:08 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 [this message]
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
  -- 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=1055128068.8987.185.camel@simple \
    --to=solar@gentoo.org \
    --cc=gentoo-dev@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