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, 61 deletions

diff --git a/meta/files/common-licenses/ECL-1 b/meta/files/common-licenses/ECL-1
deleted file mode 100644
index 3f582988fe..0000000000
--- a/meta/files/common-licenses/ECL-1
+++ /dev/null
@@ -1,61 +0,0 @@
-
-This Educational Community License (the "License") applies
-to any original work of authorship (the "Original Work") whose owner
-(the "Licensor") has placed the following notice immediately
-following
-the copyright notice for the Original Work:
-
-Copyright (c) <year> <copyright holders>
-
-Licensed under the Educational Community License version 1.0
-
-This Original Work, including software, source code, documents,
-or other related items, is being provided by the copyright holder(s)
-subject to the terms of the Educational Community License. By
-obtaining, using and/or copying this Original Work, you agree that you
-have read, understand, and will comply with the following terms and
-conditions of the Educational Community License:
-
-Permission to use, copy, modify, merge, publish, distribute, and
-sublicense this Original Work and its documentation, with or without
-modification, for any purpose, and without fee or royalty to the
-copyright holder(s) is hereby granted, provided that you include the
-following on ALL copies of the Original Work or portions thereof,
-including modifications or derivatives, that you make:
-
-
-The full text of the Educational Community License in a location viewable to
-users of the redistributed or derivative work.
-
-
-Any pre-existing intellectual property disclaimers, notices, or terms and
-conditions.
-
-
-
-Notice of any changes or modifications to the Original Work, including the
-date the changes were made.
-
-
-Any modifications of the Original Work must be distributed in such a manner as
-to avoid any confusion with the Original Work of the copyright holders.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
-EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
-MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
-IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
-CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
-TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
-SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
-
-The name and trademarks of copyright holder(s) may NOT be used
-in advertising or publicity pertaining to the Original or Derivative
-Works without specific, written prior permission. Title to copyright in
-the Original Work and any associated documentation will at all times
-remain with the copyright holders.
-
-
-
-
-
-