Bug 9882

Summary: recipetool: specify which licenses are unknown when multiple are found
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Paul Eggleton <bluelightning>
Component: Scripts and ToolsAssignee: Paul Eggleton <bluelightning>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: Medium CC: ross.burton, sgw
Version: 2.0   
Target Milestone: 2.2   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Don't know

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.