<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 6 March 2017 at 05:35, Trevor Woerner <span dir="ltr"><<a href="mailto:twoerner@gmail.com" target="_blank">twoerner@gmail.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="">On Thu 2017-03-02 @ 01:33:34 PM, Richard Purdie wrote:<br>
> Also, do we have any volunteers<br>
> for people who might maintain this layer in the future?<br>
<br>
</span>Could you elaborate on what you'd like to see such a maintainer do? Would the<br>
goal be to be able to create a core-image-minimal build with no GPLv3 packages<br>
and verify such an image (built for qemux86?) could boot to a prompt?</blockquote></div><br>That works currently with oe-core, the creation of the layer would just involve moving the recipes to meta-gpl2. The role of the maintainer would be to:</div><div class="gmail_extra"><br></div><div class="gmail_extra">1) Ensure that builds continue to work (i.e. adding new recipes if upstream relicenses to GPLv3)</div><div class="gmail_extra">2) Fixing security problems in the unmaintained recipes (i.e. sweeping through the CVE list and reimplementing the fix without looking at the GPLv3 fix upstream)</div><div class="gmail_extra">3) Removing recipes where possible (i.e. is it preferable to respect the license blacklist and disable readline use, or ship an old readline release with security issues)</div><div class="gmail_extra">4) Expanding coverage so that for example core-image-sato builds</div><div class="gmail_extra"><br></div><div class="gmail_extra">Ross</div><div class="gmail_extra"><br></div><div class="gmail_extra"><br></div></div>