[oe] Bitbake release
rpurdie at rpsys.net
Sat Dec 6 23:56:10 CET 2008
On Sun, 2008-12-07 at 00:13 +0200, Paul Sokolovsky wrote:
> On Sat, 06 Dec 2008 16:32:52 +0100
> Koen Kooi <k.kooi at student.utwente.nl> wrote:
> > On 06-12-08 15:39, Richard Purdie wrote:
> > > As people have probably noticed I just synced up a number of useful
> > > changes from Poky into bitbake and brought things pretty much back
> > > into sync.
> > >
> > > The current plan is to let this stabilise for 1 week and the
> > > providing no major bugs were introduced, make a new release
> > > (finally!).
> > Not a bug, but something for people to note:
> > http://projects.linuxtogo.org/pipermail/openembedded-devel/2008-October/006289.html
> I actually wonder why these (and few other) vars are not whitelisted by
Good question and there are several reasons:
1. MACHINE and DISTRO mean nothing to bitbake, they're only given
meaning by the OE metadata. Whitelisting them would mean adding them to
bitbake which is the wrong place to have knowledge of OE variables.
2. Changing variables from the environment is a risky business. If you
do that and don't invalidate the cache strange things can happen. You
can take special precautions such as making the cache path MACHINE
specific which "solves" the problem. Not every configuration is going to
know to do things like this.
I therefore decided that if people want to whitelist those variables and
use them from the environment, they should do so explicitly on a per
distro basis. Most distros and developers have environment setup scripts
and those scripts are the right place to make this kind of choice.
Hardcoding it into bitbake would be a bad thing.
Note that there is a list of variables that bitbake does auto whitelist
which is in lib/bb/utils.py. Those variables are common system variables
like PATH, not OE specific ones like MACHINE or DISTRO though.
More information about the Openembedded-devel