<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Sep 29, 2015 at 2:21 AM, Tim Jaacks <span dir="ltr"><<a href="mailto:tim.jaacks@garz-fricke.com" target="_blank">tim.jaacks@garz-fricke.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> Remember that _remove is usable in global configuration context as well. We<br>
> need the user to be able to remove something from local.conf which added in<br>
> a recipe, but if we blindly follow the order of append/prepend/remove<br>
> operations, it wouldn't work as expected, as the configuration metadata is<br>
> parsed long before the recipes.<br>
<br>
</span>Why would that be a problem? Of course the global configuration in local.conf should have a higher priority than all the layers. What I would expect is a chain of _append and _remove operations, ordered by layer priority, and with the overrides in local.conf being applied at the very end.</blockquote></div><br>That's not how the bitbake metadata works. Hardcoding an assumption that local.conf is magic is not how we do things. local.conf is *not* special. It's a config file that happens to be included by bitbake.conf, among many other .confs it also includes.<br>-- <br><div class="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>