From: Brad Laue <brad@brad-x.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] apache.eclass proposed
Date: Mon, 09 Jun 2003 13:23:49 -0400 [thread overview]
Message-ID: <3EE4C2A5.9070600@brad-x.com> (raw)
In-Reply-To: <20030609060131.GA2683@cherenkov.orbis-terrarum.net>
Robin H.Johnson wrote:
> I believe that would be a better solution than looking for the
> DocumentRoot they have set. As an example, I run a couple of webservers
> at work. Their DocumentRoot is /var/www, which is a read-only NFS mount.
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 don't think we should remove this. If there are ebuilds that don't
comply with this method of finding out where the documentroot is, they
can be fixed all the more easily using an eclass.
> One further thing with the DocumentRoot issue. Say I have two systems
> that share binary packages, but they have different DocumentRoot
> settings. I create the binary tbz2 on the first system, and it packages
> everything up with the first path, say /home/httpd/htdocs. Then I want
> to also install on the second system, which has a DocumentRoot of
> /var/www. The files would still be installed to /home/httpd/htdocs,
> defeating the purpose of your check for the DocumentRoot setting.
Is pkg_preinst observed when emerging a .tbz2 package? This would be
another thing to change about the ebuilds in question.
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.
Brad
--
// -- http://www.BRAD-X.com/ -- //
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-06-09 17:23 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 [this message]
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=3EE4C2A5.9070600@brad-x.com \
--to=brad@brad-x.com \
--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