On Sun, Mar 13, 2005 at 03:48:03PM +0000, Ciaran McCreesh wrote:
> On Sun, 13 Mar 2005 09:40:16 -0600 Brian Harring <ferringb@gentoo.org>
> wrote:
> | Assuming no one can come up with a valid reason why the entire user
> | env must be dumped into the compilation  environment, whitelisting of
> | vars that are allowed in would be the next step.  LINGUAS,
> | EXTRA_ECONF, etc.
> 
> Will this whitelist be developer-controllable, or will we have to wait
> several years any time we want something added to it?
At the moment, was thinking of having it be a stackable list, defaults supplied by portage, *potentially* profiles 
can override/adjust it, and ebuilds themselves can request vars be brought in- note that's only possible *after* 
sourcing the ebuild.  Shouldn't be an issue anyways, cause people don't do evil things like env based 
settings/adjustments in the global scope, right? :)

Re: portage controlling things, not the intention.  Wouldn't be trying to move bin/* code into the tree if it were.
~harring