Skip to contentSkip to conversation

RFC: Upgrade OE.dev to bitbake 1.8.8

DISCUSSION Richard Purdie 6 participants 10 messages Aug 21, 2007 – Aug 31, 2007

lore
Share & tools
lore
#0 lore raw

Hi,

There are lots of good changes in bitbake 1.8.8. Providing no major issues are found with that bitbake release should we make it the minimum version requirement for OE.dev in say two weeks? Any objections?

Regards,

Richard

#1 lore raw
Quoted 5 lines · Richard Purdie

Hi,

There are lots of good changes in bitbake 1.8.8. Providing no major issues are found with that bitbake release should we make it the minimum version requirement for OE.dev in say two weeks? Any objections?

It builds angstrom-console-image for my arm targets. So the little I use it for I have no objections. :)

Quoted 13 lines

Regards,

Richard

_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

#2 lore raw
In reply to Richard Purdie

Works for me too, as far as I can tell. The package in question turned out to be pysqlite on gentoo (just for the record).

Love,
H

Quoted 17 lines · Richard Purdie

Hi,

There are lots of good changes in bitbake 1.8.8. Providing no major issues are found with that bitbake release should we make it the minimum version requirement for OE.dev in say two weeks? Any objections?

Regards,

Richard

_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

#3 lore raw
In reply to Richard Purdie

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Richard Purdie schreef:

Quoted 5 lines

Hi,

There are lots of good changes in bitbake 1.8.8. Providing no major issues are found with that bitbake release should we make it the minimum version requirement for OE.dev in say two weeks? Any objections?

Let's activate it on 20070904

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFGzDdzMkyGM64RGpERAiTnAJ4oLpzp1ooBpt5EpxsYRoM1Jcc2wQCfZczH N1lf6gH7oJEVFlvdpBfWsio=
=z44F
-----END PGP SIGNATURE-----

#4 lore raw
Quoted 8 lines · Koen Kooi

Richard Purdie schreef:

Quoted 5 lines

Hi,

There are lots of good changes in bitbake 1.8.8. Providing no major issues are found with that bitbake release should we make it the minimum version requirement for OE.dev in say two weeks? Any objections?

Let's activate it on 20070904

+1.

Regards,

:M:

Signature · 1 line
Michael 'Mickey' Lauer | IT-Freelancer | http://www.vanille-media.de
#5 lore raw

Hello,

Quoted 10 lines · Dr. Michael Lauer
Quoted 8 lines · Koen Kooi

Richard Purdie schreef:

Quoted 5 lines

Hi,

There are lots of good changes in bitbake 1.8.8. Providing no major issues are found with that bitbake release should we make it the minimum version requirement for OE.dev in say two weeks? Any objections?

Let's activate it on 20070904

Are the OE->bitbake version-dependencies documented or tagged anywhere?

If not yet, I would propose to tag the OE repository with a tag like "PRE-BITBAKE-1_8_8" or whatever is supported/desired for mtn/oe.

Regards,

Leon.

#6 lore raw
Quoted 4 lines · Leon Woestenberg

Are the OE->bitbake version-dependencies documented or tagged anywhere?

If not yet, I would propose to tag the OE repository with a tag like "PRE-BITBAKE-1_8_8" or whatever is supported/desired for mtn/oe.

$ cat conf/sanity.conf | grep VER
BB_MIN_VERSION = "1.8.5"

Cheers,

Richard

#7 lore raw

Hello Richard, all,

Quoted 9 lines · Richard Purdie
Quoted 4 lines · Leon Woestenberg

Are the OE->bitbake version-dependencies documented or tagged anywhere?

If not yet, I would propose to tag the OE repository with a tag like "PRE-BITBAKE-1_8_8" or whatever is supported/desired for mtn/oe.

$ cat conf/sanity.conf | grep VER
BB_MIN_VERSION = "1.8.5"

This describes that, given a OE checkout, which bitbake I need minimally.

Now, suppose I have a given bitbake version, how do I find out which OE revision should work with it?

My proposal is to tag the OE tree on 2007-09-03.

Regards,

Signature · 1 line
Leon
#8 lore raw
Quoted 9 lines
Quoted 5 lines
Quoted 2 lines

If not yet, I would propose to tag the OE repository with a tag like "PRE-BITBAKE-1_8_8" or whatever is supported/desired for mtn/oe.

$ cat conf/sanity.conf | grep VER
BB_MIN_VERSION = "1.8.5"

This describes that, given a OE checkout, which bitbake I need minimally.

Now, suppose I have a given bitbake version, how do I find out which OE revision should work with it?

mtn log? ;-)

Quoted 1 line

My proposal is to tag the OE tree on 2007-09-03.

It's not that I object the tag, but what's the use of it? I mean, I don't think OE is something you may possibly want to stick to old revision of?

Love,
H

#9 lore raw

Michael,

Quoted 10 lines · Michael Krelin
Quoted 9 lines
Quoted 5 lines
Quoted 2 lines

If not yet, I would propose to tag the OE repository with a tag like "PRE-BITBAKE-1_8_8" or whatever is supported/desired for mtn/oe.

$ cat conf/sanity.conf | grep VER
BB_MIN_VERSION = "1.8.5"

This describes that, given a OE checkout, which bitbake I need minimally.

Now, suppose I have a given bitbake version, how do I find out which OE revision should work with it?

Quoted 8 lines

mtn log? ;-)

Quoted 1 line

My proposal is to tag the OE tree on 2007-09-03.

It's not that I object the tag, but what's the use of it? I mean, I don't think OE is something you may possibly want to stick to old revision of?

I found it too hard to combine
1) tracking OE changes
2) develop against OE.

time-wise in an environment where reproducability and deterministic builds are top-priority. My current practice is to have both a frozen and a current project for each target.

So yes, I would like to be able to freeze against something. No biggie though. Never mind my request,

Signature · 1 line
Leon