aboutsummaryrefslogtreecommitdiffstats
path: root/scripts/lib/devtool/standard.py
diff options
context:
space:
mode:
authorPaul Eggleton <paul.eggleton@linux.intel.com>2016-10-28 15:47:40 +1300
committerPaul Eggleton <paul.eggleton@linux.intel.com>2016-10-31 16:57:35 +1300
commitdaa1ccf7c131f983aa98b7dd64676251a9f0cf6b (patch)
tree4a9b82c1048cd6cdd2dfaffb4d6c8dfa32a238e3 /scripts/lib/devtool/standard.py
parent299bdc10f6f62885565d15669097dae33cc60081 (diff)
downloadopenembedded-core-contrib-daa1ccf7c131f983aa98b7dd64676251a9f0cf6b.tar.gz
openembedded-core-contrib-daa1ccf7c131f983aa98b7dd64676251a9f0cf6b.tar.bz2
openembedded-core-contrib-daa1ccf7c131f983aa98b7dd64676251a9f0cf6b.zip
recipetool: create: separate LICENSE items with & by default
recipetool sets the LICENSE value based on licenses detected from the source tree. If there are multiple licenses then they were being separated by spaces, but this isn't actually legal formatting and if you're using "devtool add" you get a warning printed when devtool parses the recipe internally. Earlier I had made a conscious decision to do it this way since it's up to the user to figure out whether the multiple licenses should all apply (in which case they'd be separated with &) or if there is a choice of license (in which case | is the correct separator). However, I've come to the conclusion that we can just default to & and then the ugly warning goes away, and it's the safest alternative of the two (and most likely to be correct, since it's more common to have a codebase which is made up of code with different licenses, i.e. all of them apply to the combined work). I've tweaked the comment that we add to the recipe to explicitly state that we've used & and that the user needs to change that if that's not accurate. Fixes [YOCTO #10413]. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Diffstat (limited to 'scripts/lib/devtool/standard.py')
0 files changed, 0 insertions, 0 deletions