<div dir="ltr">On 30 August 2017 at 16:13, Trevor Woerner <span dir="ltr"><<a href="mailto:twoerner@gmail.com" target="_blank">twoerner@gmail.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Wed, Aug 30, 2017 at 6:53 AM, Burton, Ross <<a href="mailto:ross.burton@intel.com">ross.burton@intel.com</a>> wrote:<br>
> Note that we've reached feature freeze for 2.4 so this will have to wait for<br>
> 2.5.<br>
<br>
</span>A lot of my builds failed last night because I'm not including<br>
meta-networking (which pulls in meta-python) because they weren't<br>
needed previously for what I was building. But with libmnl now being<br>
needed by iproute2, maybe this is a stronger argument for needing it<br>
in oecore for this release? oecore should stand on its own, unless<br>
there's a way to make this dependency a non-default packageconfig?<br>
<br>
It's not a big deal, I can just add meta-networking and meta-python<br>
and "solve" the problem.</blockquote><div><br></div><div>How and why does oe-core need libmnl?</div><div><br></div><div>Ross </div></div></div></div>