On Friday 08 May 2015 09:40:48 Otavio Salvador wrote: > On Fri, May 8, 2015 at 9:39 AM, Paul Eggleton > > <[email protected]> wrote: > > On Friday 08 May 2015 13:07:35 Steffen Sledz wrote: > >> Since switching from dizzy to fido we've some warnings related to some of > >> our own closed source packages. > >> > >> WARNING: log_check: There is a warn message in the logfile > >> WARNING: log_check: Matched keyword: [WARNING:] > >> WARNING: log_check: WARNING: The license listed CLOSED was not in the > >> licenses collected for foo > >> > >> The recipes contain lines like this one: > >> > >> LICENSE = "CLOSED" > >> > >> How should we fix the recipe to avoid the warning? > > > > I think the part of the code that produces this warning probably should be > > ignoring the CLOSED value. Can I ask you to please file a bug? Feel free > > to add me on CC. > > You can use proprietary.
If you mean "Proprietary", yes there is a common license file for that but then I believe you will get an error if LIC_FILES_CHKSUM is not set in the recipe. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
