Re: sstate environment variable whitelist

[Richard Purdie <rpurdie@linux.intel.com>]

On Tue, 2010-11-23 at 14:54 +0000, Paul Eggleton wrote:
> Hi all,
> 
> I'm taking a look into the sstate functionality. Looking at the
> changes Kevin has made in his tk/sstate branch and the environments my
> own two systems (Fedora 14 & Kubuntu 10.10) I note that there are
> still quite a lot of variables that are not whitelisted out. The
> question is do we expect to whitelist out absolutely all environment
> variables we don't care about on as many possible host distributions
> as possible? Or do we only selectively whitelist out those that we
> expect to change frequently (those that point to PIDs, session IDs,
> usernames etc.)?

There is a know list of variable we allow into the build environment, so
its a finite list we need to cover. That list is the combination of the
whitelist in the environment script and the one in lib/bb/utils.py.

I'd actually like to stop exporting a lot of the white listed variables
to every task and start being more selective. The sstate/siggen code
should then stop picking them up as dependencies.

Cheers,

Richard