Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org
Subject: Re: Bitbake release
Date: Sat, 06 Dec 2008 22:56:10 +0000	[thread overview]
Message-ID: <1228604170.5375.14.camel@dax.rpnet.com> (raw)
In-Reply-To: <20081207001358.17e45205@widy.localdomain>

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@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
> default.

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.

Cheers,

Richard






  reply	other threads:[~2008-12-06 23:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-06 14:39 Bitbake release Richard Purdie
2008-12-06 15:32 ` Koen Kooi
2008-12-06 17:50   ` Tom Rini
2008-12-06 18:23     ` Koen Kooi
2008-12-06 22:13   ` Paul Sokolovsky
2008-12-06 22:56     ` Richard Purdie [this message]
2008-12-08 10:37   ` Koen Kooi
2008-12-16 13:19     ` Holger Freyther

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=1228604170.5375.14.camel@dax.rpnet.com \
    --to=rpurdie@rpsys.net \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.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