license: manifest and license path

This is a fairly large commit, so I want to step through some of
what this accomplishes:

1. Additional licenses

I've added/modified/corrected some of the common licenses
within OE-core in prep. for a major license audit. Most of these
are in SPDX format. A few, there is no OSI equivalent.

2. Additional SPDX mappings

I've added some additional SPDX mappings to account for removing
some duplicate licenses. (ie GPL-2 and GPL-2.0 were the same)
I've also remapped a few things to more accurately reflect what
they should be pointing at.

Note: Artistic/LGPL/GPL/MPL. Quite a few LICENSE fields list these
licenses. They make no sense and need auditing. In a future commit
I have some fixes to particularly egregious LICENSE fields, but
a full audit should be done. I've listed to obvious candidates at:

https://wiki.yoctoproject.org/wiki/License_Audit

3. License manifest

We now have a license manifest generation that occurs in rootfs for
everything BUT .deb. This requires the changes Paul Eggleton has
done to rootfs_* particularly the list_installed_packages function.
The manifest is accurate during a parallel bitbake now (Weee!) and
is prime for my planned SPDX format manifest during the next period.

4. License manifest on image.

We also want the ability to add licenses to the image. This
functionality is also in base-files and will be stripped out in my
next commit. The manifest is not added by default and is a two var
setting in license.conf:

If I want *just* the manifest on the image (small) then I set:
COPY_LIC_MANIFEST = "1"

This copies the manifest to:

/usr/share/common-licenses/license.manifest

If I want the actual PKG license text on the image (much larger)
I need to set both both COPY_LIC_MANIFEST and COPY_LIC_DIRS in
license.conf. This will create:

/usr/share/common-licenses/(package name)/(licenses in LIC_SRC_URI)

Word of warning. This can be larger than wanted depending on image
and is probably ripe for linking licenses, but I ran out of time this
week to get that done.

5. Custom License search path.

We now have the ability to add licenses to the build without touching
common-licenses. This is set via license.conf:

LICENSE_PATH += "/path/to/custom/licenses"

You want to make sure the license is unique. license.bbclass picks the
first license it finds.

(From OE-Core rev: 558b5043e1d5a36caff137093fd04abcf025af1c)

Signed-off-by: Elizabeth Flanagan <elizabeth.flanagan@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

1 files changed, 0 insertions, 53 deletions

diff --git a/meta/files/common-licenses/Simple-2 b/meta/files/common-licenses/Simple-2
deleted file mode 100644
index 4a2e1c3bac..0000000000
--- a/meta/files/common-licenses/Simple-2
+++ /dev/null
@@ -1,53 +0,0 @@
-
-Simple Public License (SimPL)
-
-Preamble
-This Simple Public License 2.0 (SimPL 2.0 for short) is a plain language
-implementation of GPL 2.0. The words are different, but the goal is the same -
-to guarantee for all users the freedom to share and change software. If anyone
-wonders about the meaning of the SimPL, they should interpret it as consistent
-with GPL 2.0.
-Simple Public License (SimPL) 2.0
-The SimPL applies to the software's source and object code and comes with any
-rights that I have in it (other than trademarks). You agree to the SimPL by
-copying, distributing, or making a derivative work of the software.
-
-You get the royalty free right to:
-Use the software for any purpose;
-Make derivative works of it (this is called a "Derived Work");
-Copy and distribute it and any Derived Work.
-If you distribute the software or a Derived Work, you must give back to the
-community by:
-Prominently noting the date of any changes you make;
-Leaving other people's copyright notices, warranty disclaimers, and license
-terms in place;
-Providing the source code, build scripts, installation scripts, and interface
-definitions in a form that is easy to get and best to modify;
-Licensing it to everyone under SimPL, or substantially similar terms (such as
-GPL 2.0), without adding further restrictions to the rights provided;
-Conspicuously announcing that it is available under that license.
-There are some things that you must shoulder:
-You get NO WARRANTIES. None of any kind;
-If the software damages you in any way, you may only recover direct damages up
-to the amount you paid for it (that is zero if you did not pay anything). You
-may not recover any other damages, including those called "consequential
-damages." (The state or country where you live may not allow you to limit
-your liability in this way, so this may not apply to you);
-The SimPL continues perpetually, except that your license rights end
-automatically if:
-You do not abide by the "give back to the community" terms (your
-licensees get to keep their rights if they abide);
-Anyone prevents you from distributing the software under the terms of the
-SimPL.
-License for the License
-You may do anything that you want with the SimPL text; it's a license form to
-use in any way that you find helpful. To avoid confusion, however, if you
-change the terms in any way then you may not call your license the Simple
-Public License or the SimPL (but feel free to acknowledge that your license is
-"based on the Simple Public License").
-
-
-
-
-
-