Bug 9882 - recipetool: specify which licenses are unknown when multiple are found
Summary: recipetool: specify which licenses are unknown when multiple are found
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: Scripts and Tools (show other bugs)
Version: 2.0
Hardware: x86 Multiple
: Medium enhancement
Target Milestone: 2.2
Assignee: Paul Eggleton
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-07-06 04:33 UTC by Paul Eggleton
Modified: 2016-07-26 10:10 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Eggleton 2016-07-06 04:33:22 UTC
Often, multiple license files are picked up when scanning a source tree, and some of these will not be able to be mapped to a known license - this is particularly true when creating recipes for node.js modules. These unknown licenses are squashed down to a single "Unknown" entry in the LICENSE value within the created recipe, which isn't very helpful if you want to go and find just those. We should add an explicit comment within the recipe about which license files couldn't be mapped to a LICENSE entry.