Skip to contentSkip to conversation

LICENSE: Clarify what is meant by 'metadata'

PATCH In review Saul Wold 2 participants 3 messages Feb 27, 2017 – Feb 28, 2017

lore
Share & tools
lore

Saul Wold

author
#0 lore raw

PATCH 1/1 LICENSE: Clarify what is meant by 'metadata'

The term metadata in the LICENSE text is unclear and recently garnered some questions at ELC, so clarify metadata to include bbclasses, which is and has been metadata as well as code.

---
 LICENSE | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)
LICENSE +5 -3
index 21fa6e6..9783ee5 100644
@@ -6,9 +6,11 @@ meta/COPYING.MIT (MIT)
 meta-selftest/COPYING.MIT (MIT)
 meta-skeleton/COPYING.MIT (MIT)
 
-All metadata is MIT licensed unless otherwise stated. Source code
-included in tree for individual recipes is under the LICENSE stated in
-the associated recipe (.bb file) unless otherwise stated.
+All metadata files (including, but not limited to bb, bbappend,
+bbclass, inc and conf files) are MIT licensed unless otherwise stated.
+Source code included in tree for individual recipes is under the
+LICENSE stated in the associated recipe (.bb file) unless otherwise
+stated.
 
 License information for any other files is either explicitly stated 
 or defaults to GPL version 2.
Signature · 1 line
2.7.4
#1 lore raw
Quoted 6 lines · Saul Wold

The term metadata in the LICENSE text is unclear and recently garnered some questions at ELC, so clarify metadata to include bbclasses, which is and has been metadata as well as code.

This breaks other layers (including meta-intel and meta-qt), do you have corresponding patches?

Ross

author
#2 lore raw
Quoted 6 lines · Ross
Quoted 4 lines · Saul Wold

The term metadata in the LICENSE text is unclear and recently garnered some questions at ELC, so clarify metadata to include bbclasses, which is and has been metadata as well as code.

Quoted 6 lines
Quoted 2 lines

This breaks other layers (including meta-intel and meta-qt), do you have corresponding patches?

Oh man, I did not consider recipes using the OE-Core LICENSE file as a LIC_CHKSUM_FILE, that's sort of wrong on almost all cases except maybe the build-appliance or some containers that also contain OE-Core meta- data.

Layers particularly should not use OE-Core's LICENSE, so fixes to layers will go first.

V2 coming when those are merged.

Sau!

Quoted 1 line

Ross