<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jun 8, 2016 at 3:24 PM, 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 Wed, 2016-06-08 at 16:15 -0500, Mark Hatle wrote:<br>
> In addition, many of the layers I work with have a clear set of<br>
> required layers<br>
> (LAYERDEPENDS), but also have 'recommended' layers... So I'd love to<br>
> see a<br>
> LAYERRECOMMENDS as well.<br>
<br>
> For this one, in bitbake, we could add the LAYERRECOMMENDS to the<br>
> priority<br>
> sorting code -- but if the layer is not included it's not an error or<br>
> warning.<br>
<br>
</span>I don't understand this. Why would the fact a layer recommends another<br>
layer change priority sorting code? I don't think the dependency<br>
variable does that?<br>
<br>
I get the feeling I'm missing something from this proposal...<br></blockquote></div><br>Layer priorities *are* influenced by dependent layers. I know for sure it does when no priority is specified, can't recall if it does when is specified as well. It boosts the priority of a layer if it depends on a high priority layer.</div><div class="gmail_extra"><br></div><div class="gmail_extra">I do think recommended layers would be useful, I'd considered proposing that just a week or two ago.<br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">Christopher Larson<br>clarson at kergoth dot com<br>Founder - BitBake, OpenEmbedded, OpenZaurus<br>Maintainer - Tslib<br>Senior Software Engineer, Mentor Graphics</div>
</div></div>