public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Donny Davies <woodchip@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] apache.eclass proposed
Date: Mon, 9 Jun 2003 23:02:05 -0400	[thread overview]
Message-ID: <20030610030204.GA31790@breccia.escarpment> (raw)
In-Reply-To: <3EE4C2A5.9070600@brad-x.com>

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


  reply	other threads:[~2003-06-10  3:02 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 [this message]
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=20030610030204.GA31790@breccia.escarpment \
    --to=woodchip@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