2011/10/17 Khem Raj <raj.k...@gmail.com> > On 10/16/2011 11:35 PM, Frans Meulenbroeks wrote: > >> >> >> 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 >
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. > > 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. > 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 _______________________________________________ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel