Re: [OE-core] Layer priorities influencing default version selection
On Tue, 2011-08-02 at 14:45 +0100, Richard Purdie wrote: We could do with clearly documenting this in the bitbake manual. I suspect users would expect the highest version to win and we probably should change the behaviour but I'm open to other opinions. The original intent with BBFILE_COLLECTIONS was that the recipe from the highest-priority collection would win even if it was an older version. (The rationale for this was that the one in the higher priority collection was the most likely to have local customisations, and you wouldn't want those to suddenly be negated if a newer version popped up in some upstream collection.) I suspect the same logic probably does apply to layers to some extent for the same reason. If there is a situation where you are just trying to aggregate the recipes together from a bunch of layers and you just want the highest version from that set then my first reaction would be that the layers should probably all have the same priority. Actually, to some extent I consider it a bit of a misfeature that the layer priority is specified by the layer rather than by the user in bblayers.conf, since this makes it harder to vary the stack-up order without local hackery to the layer files. For example, meta-oe currently sets itself to a higher priority than oe-core, but I've found that it generally seems to suit me better if meta-oe is actually the lower-priority layer. p. ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] Layer priorities influencing default version selection
On Tue, Aug 2, 2011 at 6:52 AM, Phil Blundell ph...@gnu.org wrote: Actually, to some extent I consider it a bit of a misfeature that the layer priority is specified by the layer rather than by the user in bblayers.conf, since this makes it harder to vary the stack-up order without local hackery to the layer files. For example, meta-oe currently sets itself to a higher priority than oe-core, but I've found that it generally seems to suit me better if meta-oe is actually the lower-priority layer. Agreed. It also means that the priority knowledge is split between layer.conf and bblayers.conf today, as config/class priority is determined by order of entries in BBLAYERS, whereas recipe priority is determined by layer.conf. -- Christopher Larson clarson at kergoth dot com Founder - BitBake, OpenEmbedded, OpenZaurus Maintainer - Tslib Senior Software Engineer, Mentor Graphics ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
