From: Brian Harring <ferringb@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] whitelisting the env ebuilds execute in
Date: Sun, 13 Mar 2005 17:05:31 -0600 [thread overview]
Message-ID: <20050313230531.GE19847@freedom.wit.com> (raw)
In-Reply-To: <1110752415.11273.29.camel@localhost>
On Sun, Mar 13, 2005 at 05:20:15PM -0500, Ned Ludd wrote:
> So it will be something like $PORTDIR/profiles/env.accept.list in which
> all devs should be able to add to as needed vs having to file bugs and
> wait for long periods of time?
Yeah, pretty much.
Whatever y'all want it to be, I'm just getting bloody sick of seeing 200+ vars in an ebuild execution env, whenever I
have to go digging into the guts of it. Beyond that, it is (afaik) a good source of screwy bugs- random user vars
screwing with things that aren't expected/accounted for. A blacklist approach isn't sane there, too many
possibilities.
Not sure who it was who mentioned it (marienz, was that you?), but a per-ebuild GRAB_USER_VARS would likely be sane
also- that would be checked by the ebuild_processor, and the env var would be set. This is post sourcing however-
before setup phase.
~harring
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-03-13 23:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-13 15:40 [gentoo-dev] whitelisting the env ebuilds execute in Brian Harring
2005-03-13 15:48 ` Ciaran McCreesh
2005-03-13 16:04 ` Brian Harring
2005-03-13 22:20 ` Ned Ludd
2005-03-13 23:05 ` Brian Harring [this message]
2005-03-13 23:24 ` Thomas de Grenier de Latour
2005-03-15 9:03 ` Sven Vermeulen
2005-03-14 19:21 ` Aron Griffis
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=20050313230531.GE19847@freedom.wit.com \
--to=ferringb@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-dev@robin.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