[OE-core] [PATCH] image.bbclass: allow override of image LICENSE

Burton, Ross ross.burton at intel.com
Wed Oct 11 10:35:21 UTC 2017


On 10 October 2017 at 21:56, Paul Eggleton <paul.eggleton at linux.intel.com>
wrote:

> Sorry to dredge this up, but when do you see the need to specify a
> different
> image LICENSE?
>
> Logically, an image recipe's LICENSE can only refer to the recipe itself
> and
> whatever files might be pulled in by it directly (usually none, but some
> people re-enable do_fetch and do_unpack to allow this), since otherwise the
> contents of the image are covered by the licenses of all of the recipes
> that
> build the packages that go into it, and we already assemble a license
> manifest
> for the image to cover those. Does that match your interpretation?
>

In the general case this is true but I guess rootfs postinstall hooks can
create file which are not covered by the package licenses.

Ross
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20171011/0b2d05a4/attachment-0002.html>


More information about the Openembedded-core mailing list