<div dir="ltr"><div><div>We have this variable appearing in a couple manuals BTW. If anyone has any feedback on what is being said here I can update.<br><br></div>Thanks,<br></div>Scott<br><br><a href="https://www.yoctoproject.org/docs/2.5/ref-manual/ref-manual.html#var-LAYERSERIES_COMPAT">https://www.yoctoproject.org/docs/2.5/ref-manual/ref-manual.html#var-LAYERSERIES_COMPAT</a><br><a href="https://www.yoctoproject.org/docs/2.5/dev-manual/dev-manual.html#creating-your-own-layer">https://www.yoctoproject.org/docs/2.5/dev-manual/dev-manual.html#creating-your-own-layer</a><br><br><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Apr 6, 2018 at 8:29 AM, Richard Purdie <span dir="ltr"><<a href="mailto:richard.purdie@linuxfoundation.org" target="_blank">richard.purdie@linuxfoundation.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Fri, 2018-04-06 at 10:16 -0400, Trevor Woerner wrote:<br>
> A) Some layers only switch to an official branch name when the find a<br>
> reason to. E.g. branch "sumo" is created on openembedded-core but<br>
> meta-A keeps working on master unless an incompatible change is<br>
> created in openembedded-core that forces meta-A to create a "sumo"<br>
> branch.<br>
><br>
> B) Other layers create official branches the moment they exist. E.g.<br>
> branch "sumo" is created on openembedded-core and meta-B instantly<br>
> creates a "sumo" branch to mark this point in time, and continues<br>
> working on master. If meta-B's "sumo" branch fails to build against<br>
> openembedded-core's "sumo" branch because an incompatible change is<br>
> made to openembedded-core's sumo branch, meta-B fixes the issue on<br>
> the sumo branch.<br>
><br>
><br>
> I can see how the change you've implemented will be very useful for<br>
> the A)<br>
> cases. Will it be needed for the B) cases? In other words, does the<br>
> code<br>
> you're adding implicitly assume:<br>
><br>
> LAYERSERIES_COMPAT_<...> = "layer"<br>
><br>
> for any given "layer"?<br>
<br>
</span>No, there is no implicit assumption.<br>
<br>
In both A) and B) cases the maintainer adds the new "codename" to the<br>
list of compatible layer series in LAYERSERIES_COMPAT_<layer> for their<br>
layer. They can list multiple layers in there, e.g. "rocko sumo".<br>
<br>
The one annoying thing about all this is the layer maintainers do have<br>
to update layer.conf each time a new release codename comes out. I<br>
think that is a reasonable compromise to be able to give users a much<br>
better idea of which layers are compatible or incomaptible with their<br>
setup though. It means someone has looked at it and believes it will<br>
work with a given release series.<br>
<br>
Just to be clear, "layer" would never be a valid value there, it will<br>
always be the release/branch codenames.<br>
<br>
Cheers,<br>
<br>
Richard<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
______________________________<wbr>_________________<br>
Openembedded-architecture mailing list<br>
<a href="mailto:Openembedded-architecture@lists.openembedded.org">Openembedded-architecture@<wbr>lists.openembedded.org</a><br>
<a href="http://lists.openembedded.org/mailman/listinfo/openembedded-architecture" rel="noreferrer" target="_blank">http://lists.openembedded.org/<wbr>mailman/listinfo/openembedded-<wbr>architecture</a><br>
</div></div></blockquote></div><br></div>