recipetool: create: fix for regression in npm license handling
OE-Core commit c0cfd9b1d54b05ad048f444d6fe248aa0500159e added handling for AND / OR in license strings coming from npm, but made the assumption that an & would always be present in the license value. Check if it's there first so we don't fail if it isn't. (From OE-Core rev: abe2955df2dc558de6068d9373dfcb47d690704b) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
parent
9dc4707035
commit
0440cbccda
|
@ -240,7 +240,8 @@ class NpmRecipeHandler(RecipeHandler):
|
|||
packages['${PN}'] = ''
|
||||
pkglicenses = split_pkg_licenses(licvalues, packages, lines_after, licenses)
|
||||
all_licenses = list(set([item.replace('_', ' ') for pkglicense in pkglicenses.values() for item in pkglicense]))
|
||||
all_licenses.remove('&')
|
||||
if '&' in all_licenses:
|
||||
all_licenses.remove('&')
|
||||
# Go back and update the LICENSE value since we have a bit more
|
||||
# information than when that was written out (and we know all apply
|
||||
# vs. there being a choice, so we can join them with &)
|
||||
|
|
Loading…
Reference in New Issue