[Openembedded-architecture] Separating out old gplv2 recipes into their own layer
Burton, Ross
ross.burton at intel.com
Mon Mar 6 10:56:57 UTC 2017
On 6 March 2017 at 05:35, Trevor Woerner <twoerner at gmail.com> wrote:
> On Thu 2017-03-02 @ 01:33:34 PM, Richard Purdie wrote:
> > Also, do we have any volunteers
> > for people who might maintain this layer in the future?
>
> Could you elaborate on what you'd like to see such a maintainer do? Would
> the
> goal be to be able to create a core-image-minimal build with no GPLv3
> packages
> and verify such an image (built for qemux86?) could boot to a prompt?
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:
1) Ensure that builds continue to work (i.e. adding new recipes if upstream
relicenses to GPLv3)
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)
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)
4) Expanding coverage so that for example core-image-sato builds
Ross
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-architecture/attachments/20170306/a5e9d543/attachment-0002.html>
More information about the Openembedded-architecture
mailing list