Khem Raj : binutils-cross: Sync with oe-core
A message that is not in the archive (sent off-list or not yet received): 20111015185155.DA982101FE@opal
Quoted 6 lines · On Sat, Oct 15, 2011 at 8:51 PM, <[email protected]> wrote:
Module: meta-openembedded.git
Branch: master
Commit:92b02b7209e426a70cc5626e7bdbc82052e01ac5
URL:
http://git.openembedded.org/?p=meta-openembedded.git&a=commit;h=92b02b7209e426a70cc5626e7bdbc82052e01ac5
Quoted 7 lines
Author: Khem Raj <[email protected]> Date: Sun Oct 16 01:28:32 2011 +0000binutils-cross: Sync with oe-core
Now we have own copy of binutils-cross in meta-oe
I can't unfortunately find the discussion which supposedly provided a valid reason for binutils-2.20 in meta-oe while binutils-2.21 is in oe-core. I'm against that kind of policy for meta-oe, particularly when it's about toolchain.
we need to sync with oe-core periodically
Quoted 1 line
That's just one of the bad effects :/
Quoted 5 lines
Signed-off-by Khem Raj <[email protected]>Signed-off-by Koen Kooi <[email protected]>
my 2c
Andrea
Quoted 13 lines · Andrea Adami
Quoted 11 lines · On Sat, Oct 15, 2011 at 8:51 PM, <[email protected]> wrote:
Module: meta-openembedded.git
Branch: master
Commit:92b02b7209e426a70cc5626e7bdbc82052e01ac5
URL:
http://git.openembedded.org/?p=meta-openembedded.git&a=commit;h=92b02b7209e426a70cc5626e7bdbc82052e01ac5Author: Khem Raj <[email protected]>
Date: Sun Oct 16 01:28:32 2011 +0000binutils-cross: Sync with oe-core
Quoted 7 lines
Quoted 2 lines
Now we have own copy of binutils-cross in meta-oe
I can't unfortunately find the discussion which supposedly provided a valid reason for binutils-2.20 in meta-oe while binutils-2.21 is in oe-core. I'm against that kind of policy for meta-oe, particularly when it's about toolchain.
oe-core is deprecating versions that are still used by consumers of meta-oe (mainly angstrom 2010 release)
since its toolchain and it will also benefit derivatives of angstrom. Angstrom could also move these elements
into meta-angstrom if we think that its only angstrom specific and no other consumers of oe-core needs them
layer maintainers make judgement call which they think should benefit wider community
similar but not for binutils here is a relevant thread
http://lists.linuxtogo.org/pipermail/openembedded-core/2011-October/010700.html
I think angstrom needs older binutils to support older kernels.
Quoted 19 lines
we need to sync with oe-core periodically
Quoted 1 line
That's just one of the bad effects :/
Quoted 5 lines
Signed-off-by Khem Raj <[email protected]>Signed-off-by Koen Kooi <[email protected]>my 2c
Andrea
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
2011/10/17 Khem Raj <[email protected]>
Quoted 34 lines
Quoted 7 lines · Andrea Adami
Quoted 5 lines · On Sat, Oct 15, 2011 at 8:51 PM, <[email protected]> wrote:
Module: meta-openembedded.git
Branch: master
Commit:92b02b7209e426a70cc5626e7bdbc82052e01ac5
URL:Quoted 10 lines
Quoted 8 lines
Author: Khem Raj <[email protected]> Date: Sun Oct 16 01:28:32 2011 +0000binutils-cross: Sync with oe-core
Now we have own copy of binutils-cross in meta-oe
I can't unfortunately find the discussion which supposedly provided a
valid
Quoted 3 lines
reason for binutils-2.20 in meta-oe while binutils-2.21 is in oe-core. I'm against that kind of policy for meta-oe, particularly when it's about toolchain.
oe-core is deprecating versions that are still used by consumers of meta-oe (mainly angstrom 2010 release)
since its toolchain and it will also benefit derivatives of angstrom. Angstrom could also move these elements
into meta-angstrom if we think that its only angstrom specific and no other consumers of oe-core needs them
layer maintainers make judgement call which they think should benefit wider community
Quoted 2 lines
similar but not for binutils here is a relevant thread
I feel if a distro or bsp needs a version of a package that is older than the oe-core one, it should be stored in the distro or bsp layer. Or is meta-oe also wanting to keep binutils 18.50? In oe classic this is used by the nios2 hw (and afaik there is no newer binutils supporting nios2)? I'd say if some layer needs older versions it is up to them.
What we are lacking here is a policy on purpose/goal of meta-oe and what goes in (and what not).
Frans
Quoted 36 lines · Frans Meulenbroeks
2011/10/17 Khem Raj<[email protected]>
Quoted 34 lines
Quoted 7 lines · Andrea Adami
Quoted 5 lines · On Sat, Oct 15, 2011 at 8:51 PM,<[email protected]> wrote:
Module: meta-openembedded.git
Branch: master
Commit:92b02b7209e426a70cc5626e7bdbc82052e01ac5
URL:Quoted 10 lines
Quoted 8 lines
Author: Khem Raj<[email protected]> Date: Sun Oct 16 01:28:32 2011 +0000binutils-cross: Sync with oe-core
Now we have own copy of binutils-cross in meta-oe
I can't unfortunately find the discussion which supposedly provided a
valid
Quoted 3 lines
reason for binutils-2.20 in meta-oe while binutils-2.21 is in oe-core. I'm against that kind of policy for meta-oe, particularly when it's about toolchain.
oe-core is deprecating versions that are still used by consumers of meta-oe (mainly angstrom 2010 release)
since its toolchain and it will also benefit derivatives of angstrom. Angstrom could also move these elements
into meta-angstrom if we think that its only angstrom specific and no other consumers of oe-core needs them
layer maintainers make judgement call which they think should benefit wider community
Quoted 9 lines
Quoted 2 lines
similar but not for binutils here is a relevant thread
I feel if a distro or bsp needs a version of a package that is older than the oe-core one, it should be stored in the distro or bsp layer. Or is meta-oe also wanting to keep binutils 18.50? In oe classic this is used by the nios2 hw (and afaik there is no newer binutils supporting nios2)? I'd say if some layer needs older versions it is up to them.
This is a bit different when a version is retired from oe-core there might be more than one bsp using it therefore it would be more beneficial to keep it in a common layer
Quoted 2 lines
What we are lacking here is a policy on purpose/goal of meta-oe and what goes in (and what not).
This has been discussed quite a bit when we decided to move to layered structure. meta-oe infact is an umbrella of layers and each layer can have it own development policies.
Quoted 6 lines
Frans
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
2011/10/17 Khem Raj <[email protected]>
Quoted 11 lines · Frans Meulenbroeks
Quoted 10 lines
I feel if a distro or bsp needs a version of a package that is older than the oe-core one, it should be stored in the distro or bsp layer. Or is meta-oe also wanting to keep binutils 18.50? In oe classic this is used by the nios2 hw (and afaik there is no newer binutils supporting nios2)? I'd say if some layer needs older versions it is up to them.
Quoted 4 lines
This is a bit different when a version is retired from oe-core there might be more than one bsp using it therefore it would be more beneficial to keep it in a common layer
The risk is that over time this common layer ends up being a repo with several versions of a recipe, and for some of these we end up having no idea whether or not they are used.
We've seen in oe classic to what that leads. Here, with layers being distributed it becomes even more vague what is used and what not. I'd say if oe core moves forward then a layer that is not ready to move to that new version should either keep a local copy or pin at a hash of oe-core before the recipe was removed.
BTW if I recall correctly it was discussed to have an overlap period after introducing a new version before the old one is deprecated. Not 100% sure if that was indeed decided that way.
Quoted 9 lines
What we are lacking here is a policy on purpose/goal of meta-oe and what
Quoted 2 lines
goes in (and what not).
This has been discussed quite a bit when we decided to move to layered structure. meta-oe infact is an umbrella of layers and each layer can have it own development policies.
Guess your are mixing up meta-openembedded (
http://git.openembedded.org/meta-openembedded/tree/) and meta-oe (
http://git.openembedded.org/meta-openembedded/tree/meta-oe)
(and as far as I know the policys on the common stuff (assuming we see meta-oe or meta-openembedded as common stuff) is not really documented afaik).
Btw I feel it does not really help to have some gnome stuff in meta-oe/recipes-gnome and other in meta-gnome.
Frans