[OE-core] [PATCH 3/6] yocto-compat-layer.py: apply test_signatures to all layers

[Christopher Larson]

On Mon, May 29, 2017 at 12:26 PM, Aníbal Limón <anibal.limon at linux.intel.com
> wrote:

> >
> > Changing software versions is indeed a bit more problematic. One could
> > argue that layers shouldn't fight over who provides a certain recipe in
> > the first place. If they do, perhaps the "additional layers" (= the ones
> > with lower priority) need to provide explicit .inc files with
> > PREFERRED_VERSION assignments without which the overriding recipes
> > aren't used?
>
> Yes, so in this case will need to set automatically the preferred
> versions to oe-core recipes, and then let the distro layer to change the
> preferred version in this way when test a distro layer with oe-core the
> signatures not will change only when add the combo of distro layer +
> software layer.


Currently, if you add a high priority layer with an older version recipe,
it will change the default selected recipe, lacking a PREFERRED_VERSION.
You can’t use DEFAULT_PREFERENCE to make the new old version of a recipe
not be used, since bitbake treats layer priority as more important than
default preference, so adding a .inc won’t do much good, since you can’t
make the recipe not be preferred by default without a preferred version set
to the current oe-core version. You could add such a line to the
layer.conf, but then you’re hardcoding the oe-core recipe version into a
separate layer, which is pretty ugly. I don’t htink we should be enforcing
this signature change without resolving this.
-- 
Christopher Larson
kergoth at gmail dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Senior Software Engineer, Mentor Graphics
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20170529/674cab12/attachment-0002.html>