sstate environment variable whitelist

sstate environment variable whitelist

[Paul Eggleton]

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.)?

Cheers,
Paul
---------------------------------------------------------------------
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

Re: sstate environment variable whitelist

[Richard Purdie]

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