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

diff --git a/meta/files/common-licenses/GPL-3 b/meta/files/common-licenses/GPL-3
deleted file mode 100644
index 9d9f5b03d1..0000000000
--- a/meta/files/common-licenses/GPL-3
+++ /dev/null
@@ -1,70 +0,0 @@
-
-insert GPL v3 text here
-
-GCC RUNTIME LIBRARY EXCEPTION
-Version 3.1, 31 March 2009
-
-General information:
-http://www.gnu.org/licenses/gcc-exception.html
-Copyright (C) 2009 Free Software Foundation, Inc. <http://fsf.org/>
-Everyone is permitted to copy and distribute verbatim copies of this license
-document, but changing it is not allowed.
-This GCC Runtime Library Exception ("Exception") is an additional
-permission under section 7 of the GNU General Public License, version 3
-("GPLv3"). It applies to a given file (the "Runtime
-Library") that bears a notice placed by the copyright holder of the file
-stating that the file is governed by GPLv3 along with this Exception.
-When you use GCC to compile a program, GCC may combine portions of certain GCC
-header files and runtime libraries with the compiled program. The purpose of
-this Exception is to allow compilation of non-GPL (including proprietary)
-programs to use, in this way, the header files and runtime libraries covered by
-this Exception.
-
-0. Definitions.
-A file is an "Independent Module" if it either requires the Runtime
-Library for execution after a Compilation Process, or makes use of an interface
-provided by the Runtime Library, but is not otherwise based on the Runtime
-Library.
-"GCC" means a version of the GNU Compiler Collection, with or without
-modifications, governed by version 3 (or a specified later version) of the GNU
-General Public License (GPL) with the option of using any subsequent versions
-published by the FSF.
-"GPL-compatible Software" is software whose conditions of
-propagation, modification and use would permit combination with GCC in accord
-with the license of GCC.
-"Target Code" refers to output from any compiler for a real or
-virtual target processor architecture, in executable form or suitable for input
-to an assembler, loader, linker and/or execution phase. Notwithstanding that,
-Target Code does not include data in any format that is used as a compiler
-intermediate representation, or used for producing a compiler intermediate
-representation.
-The "Compilation Process" transforms code entirely represented in
-non-intermediate languages designed for human-written code, and/or in Java
-Virtual Machine byte code, into Target Code. Thus, for example, use of source
-code generators and preprocessors need not be considered part of the
-Compilation Process, since the Compilation Process can be understood as
-starting with the output of the generators or preprocessors.
-A Compilation Process is "Eligible" if it is done using GCC, alone or
-with other GPL-compatible software, or if it is done without using any work
-based on GCC. For example, using non-GPL-compatible Software to optimize any
-GCC intermediate representations would not qualify as an Eligible Compilation
-Process.
-
-1. Grant of Additional Permission.
-You have permission to propagate a work of Target Code formed by combining the
-Runtime Library with Independent Modules, even if such propagation would
-otherwise violate the terms of GPLv3, provided that all Target Code was
-generated by Eligible Compilation Processes. You may then convey such a
-combination under terms of your choice, consistent with the licensing of the
-Independent Modules.
-
-2. No Weakening of GCC Copyleft.
-The availability of this Exception does not imply any general presumption that
-third-party software is unaffected by the copyleft requirements of the license
-of GCC.
-
-
-
-
-
-