Skip to contentSkip to conversation

Poky License Reporting

PATCH In review Beth Flanagan 2 participants 4 messages Jan 10, 2011 – Jan 13, 2011

lore
Share & tools
lore
#0 lore raw

cover Poky License Reporting

Initial commit of license reporting:

This is an intial commit for the license reporting system. A few notes:
The LICENSE fields needs to be standardized throughout poky.

I've seen a few places where Apache-v2.0 is written differently and I'm sure this will bug things out. This does not put the license data on the rootfs. I'm still working on that capability. Also, I provide both the actual license text and a link to the best guess of the generic_license. That guessing is not very robust and I'm loath to get into a bunch of pattern matching rather than standardize LICENSE.

This adds one new param to poky.conf and one new to license.bbclass:

LICENSE_DIR: the base directory we copy all the license results to (set in license.bbclass)
COMMON_LICENSE_DIR: this is the directory that holds all the common generic license files. currently meta/files/common-licenses (set in poky.conf)

TODO:
- We should verify the common-licenses. I stripped these from my Ubuntu 10.10 system.
- Enable ENABLE_ROOTFS_LICENSES. This is commented out in poky.conf. The code isn't written for it, but we should allow that capability, although the resulting image created would be a lot larger.
- More common-licenses. I don't include bzip, zlib, ICS.... I should, but that means tracking down a lot of licenses.
- General cleanup of licensing and standardization of names. We should standardize on a naming convention. What's in licenses.conf should match up with what is in the recipes which should match with what is in common-licenses. Outside the scope of this though. See:
http://bugzilla.pokylinux.org/show_bug.cgi?id=650

Pull URL: git://git.pokylinux.org/poky-contrib.git
Branch: eflanagan/license
Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=eflanagan/license

Thanks,
Beth Flanagan <[email protected]>
---

Beth Flanagan (1):
Initial commit of license reporting:

 meta/classes/license.bbclass          |   92 +++++
 meta/conf/distro/poky.conf            |    4 +-
 meta/files/common-licenses/Apache-2.0 |  202 ++++++++++
 meta/files/common-licenses/Artistic   |  131 +++++++
 meta/files/common-licenses/BSD        |   26 ++
 meta/files/common-licenses/GFDL       |  451 ++++++++++++++++++++++
 meta/files/common-licenses/GFDL-1.2   |  397 +++++++++++++++++++
 meta/files/common-licenses/GFDL-1.3   |  451 ++++++++++++++++++++++
 meta/files/common-licenses/GPL        |  676 +++++++++++++++++++++++++++++++++
 meta/files/common-licenses/GPLv2      |  339 +++++++++++++++++
 meta/files/common-licenses/GPLv3      |  676 +++++++++++++++++++++++++++++++++
 meta/files/common-licenses/LGPL       |  165 ++++++++
 meta/files/common-licenses/LGPLv2     |  481 +++++++++++++++++++++++
 meta/files/common-licenses/LGPLv2.1   |  510 +++++++++++++++++++++++++
 meta/files/common-licenses/LGPLv3     |  165 ++++++++
 15 files changed, 4765 insertions(+), 1 deletions(-)
 create mode 100644 meta/classes/license.bbclass
 create mode 100644 meta/files/common-licenses/Apache-2.0
 create mode 100644 meta/files/common-licenses/Artistic
 create mode 100644 meta/files/common-licenses/BSD
 create mode 100644 meta/files/common-licenses/GFDL
 create mode 100644 meta/files/common-licenses/GFDL-1.2
 create mode 100644 meta/files/common-licenses/GFDL-1.3
 create mode 100644 meta/files/common-licenses/GPL
 create mode 100644 meta/files/common-licenses/GPLv2
 create mode 100644 meta/files/common-licenses/GPLv3
 create mode 100644 meta/files/common-licenses/LGPL
 create mode 100644 meta/files/common-licenses/LGPLv2
 create mode 100644 meta/files/common-licenses/LGPLv2.1
 create mode 100644 meta/files/common-licenses/LGPLv3
#1 lore raw

Hi Beth,

I don't see any patches so guess you used the old-style pull script?

Quoted 4 lines · Beth Flanagan

Initial commit of license reporting:

This is an intial commit for the license reporting system. A few notes:
The LICENSE fields needs to be standardized throughout poky.

Reading this summary I'd suggest we standardise on whatever the filename in common-licenses/ is.
Furthermore we could (should) add a sanity check whereby a LICENSE field with values that aren't a file in common-licenses/ causes a warning or error.

Cheers,
Joshua

Signature · 2 lines
Joshua Lock
        Intel Open Source Technology Centre
#2 lore raw
Quoted 3 lines · Joshua Lock

Hi Beth,

I don't see any patches so guess you used the old-style pull script?

No, the patch was too big, so the listserv held it in limbo. :)

Quoted 12 lines · Beth Flanagan
Quoted 4 lines

Initial commit of license reporting:

This is an intial commit for the license reporting system. A few notes:
The LICENSE fields needs to be standardized throughout poky.

Reading this summary I'd suggest we standardise on whatever the filename in common-licenses/ is.
Furthermore we could (should) add a sanity check whereby a LICENSE field with values that aren't a file in common-licenses/ causes a warning or error.

Good point, I'll put in a check for that. A question. Could the LICENSE_FILES_CHECKSUM ever have a non file:/// URI? If so, could you point out an example of this?

-b

#3 lore raw
Quoted 20 lines · Elizabeth Flanagan
Quoted 3 lines · Joshua Lock

Hi Beth,

I don't see any patches so guess you used the old-style pull script?

No, the patch was too big, so the listserv held it in limbo. :)

Quoted 12 lines · Beth Flanagan
Quoted 4 lines

Initial commit of license reporting:

This is an intial commit for the license reporting system. A few notes:
The LICENSE fields needs to be standardized throughout poky.

Reading this summary I'd suggest we standardise on whatever the filename in common-licenses/ is.
Furthermore we could (should) add a sanity check whereby a LICENSE field with values that aren't a file in common-licenses/ causes a warning or error.

Quoted 3 lines

Good point, I'll put in a check for that. A question. Could the LICENSE_FILES_CHECKSUM ever have a non file:/// URI? If so, could you point out an example of this?

Not that I'm aware of, though we can always adjust code to handle this if required...

Cheers,
Joshua

Signature · 2 lines
Joshua Lock
        Intel Open Source Technology Centre