On 10 October 2017 at 21:56, Paul Eggleton <[email protected]> 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
-- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
