From: felix@crowfix.com
To: gentoo-portage-dev@lists.gentoo.org
Subject: [gentoo-portage-dev] Setting an env var for a specific ebuild
Date: Sun, 31 Oct 2004 08:38:51 -0800 [thread overview]
Message-ID: <20041031163851.GA32724@crowfix.com> (raw)
In-Reply-To: <20041028205247.GA26136@server.grantgoodyear.org>
I have a problem with building Apache and have not found any answers
in searching the forums or asking. Please let me know if this is not
the right place to ask.
Apache uses a wrapper called suexec to run setuid cgi programs. As
part of its security check, suexec refuses to run any program whose
location does not match a compiled-in path, which by default is
.../public_html/... Note that this path is NOT picked up from the run
time configuration, but from the build time configuration.
The net-www/apache-2.0.52-ebuild sets this build time value with an
env var:
apache_setup_vars() {
# Sets the USERDIR to default.
USERDIR="public_html"
But I have always used a different USERDIR value, and do not know how
to override this. I have resorted to editing the ebuild directly,
which means that I forget it on every upgrade and have to scratch my
head every time the first suexec program fails. I am getting quicker
at diagnosing the problem :-)
Of course editing the ebuild is not the right way to do it, but I have
not found any way of setting an override in /etc/portage or anywhere
else. I don't see how my own usr/local/portage ebuild would help; I'd
have to copy it from /usr/portage and edit anyway.
Is there a better way, or any way, to set a more-or-less permanent
override of this env var?
On an unrelated subject, rebuilding imagemagick found a conflicting
file, libltdl.a ...
media-gfx/imagemagick-6.1.0.1 (/usr/lib/libltdl.a)
sys-devel/libtool-1.5.2-r5 (/usr/lib/libltdl.a)
I have never enjoyed using bugzilla, it seems like the kind of
bureaucratic molasses that a faceless corporation would set up to show
compliance with the letter of a court order while actually
discouraging its use. Is there any other way, or has bugzilla gotten
better in the year or two since I last tried it elsewhere?
--
... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._.
Felix Finch: scarecrow repairman & rocket surgeon / felix@crowfix.com
GPG = E987 4493 C860 246C 3B1E 6477 7838 76E9 182E 8151 ITAR license #4933
I've found a solution to Fermat's Last Theorem but I see I've run out of room o
--
gentoo-portage-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-10-31 16:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-28 20:02 [gentoo-portage-dev] webapp-config and webapps Wendall Cada
2004-10-28 20:20 ` Paul de Vrieze
2004-10-28 20:34 ` Wendall Cada
2004-10-28 20:55 ` Wendall Cada
2004-10-28 21:19 ` Stuart Herbert
2004-10-28 21:28 ` Stuart Herbert
2004-10-28 21:13 ` Stuart Herbert
2004-10-28 21:48 ` Anthony Gorecki
2004-10-28 22:13 ` Stuart Herbert
2004-10-28 22:52 ` Anthony Gorecki
2004-10-28 23:31 ` Stuart Herbert
2004-10-29 1:04 ` Anthony Gorecki
2004-10-29 9:55 ` Paul de Vrieze
2004-10-30 10:17 ` Stuart Herbert
2004-10-30 21:24 ` Paul de Vrieze
2004-10-28 20:52 ` Grant Goodyear
2004-10-31 16:38 ` felix [this message]
2004-10-31 17:02 ` [gentoo-portage-dev] Setting an env var for a specific ebuild Sri Gupta
2004-10-31 18:22 ` Michael Stewart
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=20041031163851.GA32724@crowfix.com \
--to=felix@crowfix.com \
--cc=gentoo-portage-dev@lists.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