Bitbake release

Bitbake release

[Richard Purdie]

Hi,

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

Could people therefore upgrade to latest bitbake-1.8 from svn and report
any problems please. 

For reference, we will probably make OE.dev depend on the new bitbake
version pretty rapidly allowing some cleanups and optimisation unless
there are any strong objections.

Cheers,

Richard

-- 
Richard Purdie
Intel Open Source Technology Centre

Re: Bitbake release

[Koen Kooi]

On 06-12-08 15:39, Richard Purdie wrote:
> Hi,
>
> 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

regards,

Koen

Re: Bitbake release

[Tom Rini]

On Sat, Dec 06, 2008 at 04:32:52PM +0100, Koen Kooi wrote:
> On 06-12-08 15:39, Richard Purdie wrote:
>> Hi,
>>
>> 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


As I asked at the time, what's this doing?  Do all distros need to do
this?  What's Angstrom doing on the metadata side to make use of this?
Thanks!
>
-- 
Tom Rini

Re: Bitbake release

[Koen Kooi]

On 06-12-08 18:50, Tom Rini wrote:
> On Sat, Dec 06, 2008 at 04:32:52PM +0100, Koen Kooi wrote:
>> On 06-12-08 15:39, Richard Purdie wrote:
>>> Hi,
>>>
>>> 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
>
>
> As I asked at the time, what's this doing?  Do all distros need to do
> this?  What's Angstrom doing on the metadata side to make use of this?
> Thanks!

The angstrom buildscripts 
(http://cgit.openembedded.net/cgit.cgi?url=openembedded/tree/contrib/angstrom) 
pass MACHINE and ANGSTROM_MODE via the shell enviroment to avoid 
spurious reparsing. Since bitbake clean the environment the vars don't 
get into bitbake.

regards,

Koen

Re: Bitbake release

[Paul Sokolovsky]

Hello,

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:
> > Hi,
> >
> > 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.

> 
> regards,
> 
> Koen
[]

-- 
Best regards,
 Paul                          mailto:pmiscml@gmail.com

Re: Bitbake release

[Richard Purdie]

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

Re: Bitbake release

[Koen Kooi]

On 06-12-08 16:32, Koen Kooi wrote:
> On 06-12-08 15:39, Richard Purdie wrote:
>> Hi,
>>
>> 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

Hmmm, you can't pass variables containing '_' anymore:

http://cgit.openembedded.net/cgit.cgi?url=openembedded/commit/&id=325476d19b821623dbe151d7026c20dfd3754432

regards,

Koen

Re: Bitbake release

[Holger Freyther]

On Monday 08 December 2008 11:37:40 Koen Kooi wrote:

> > http://projects.linuxtogo.org/pipermail/openembedded-devel/2008-October/0
> >06289.html
>
> Hmmm, you can't pass variables containing '_' anymore:
>
> http://cgit.openembedded.net/cgit.cgi?url=openembedded/commit/&id=325476d19
>b821623dbe151d7026c20dfd3754432

Any more information? I have tagged bitbake 1.8.12 and uploaded a tarball but 
I don't know if I should "release" it...


z.