Bug 5622

Summary:	INCOMPATIBLE_LICENSE does not map licenses using SPDXLICENSEMAP
Product:	[Build System, Metadata & Runtime] OE-Core	Reporter:	Paul Eggleton <bluelightning>
Component:	core	Assignee:	Ross Burton <ross.burton>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Medium	CC:	elizabeth.flanagan, mark.hatle, meta.mr.watcher, meta.watcher, ross.burton, sgw, srifenbark
Version:	1.6
Target Milestone:	1.7
Hardware:	All
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	New (Never tested)
Verified:		Documentation change:	No (bug/feature does not impact docs)

Description Paul Eggleton 2013-12-02 12:06:33 UTC

In other parts of the licensing code, we support mapping of traditional OE LICENSE field values to their official SPDX counterparts via the SPDXLICENSEMAP variable. However, it seems with INCOMPATIBLE_LICENSE this mapping is not used; thus, if a recipe sets LICENSE = "GPL-3.0" and INCOMPATIBLE_LICENSE is set to "GPLv3" the recipe will not be excluded.

Comment 1 Ross Burton 2014-07-11 23:21:52 UTC

Just discovered this independently, this is pretty broken.

Comment 2 Scott Rifenbark 2014-07-14 07:33:35 UTC

So, 

I am marking the doc flag as "Yes" for this new bug as it seems that once this bug is fixed I need to go in and change some examples to use the SPDX names?  If this is not the case, let me know here.

Scott

Comment 3 Paul Eggleton 2014-07-14 09:41:00 UTC

Not really, no; we just need the mapping to be done in this part of the code just like it is elsewhere.

Comment 4 Scott Rifenbark 2014-07-14 09:42:20 UTC

Paul, 

Ok - resetting flag to "No"

Comment 5 Ross Burton 2014-07-14 10:25:48 UTC

Patch sent to oe-core.

Comment 6 Ross Burton 2014-07-21 10:36:31 UTC

Fixed in oe-core 5b6cdac26e35e9a3b8b09185fc16765fa99dfe5f