common-licenses: Adding new licenses and renaming

I'm adding full common licenses to the common license directory.

These licenses are taken from the SPDX project or the OSI license
repository. They conform to the SPDX naming convention and will be
used by the new license.bbclass license parser in order to maintain
some sort of internal standard for license naming.

Going forward, we should have a bigger conversation about the LICENSE
field and standardizing that to conform to this naming standard.

(From OE-Core rev: acc260418a46dadd5598c53ad3491a21e8b2d6e8)

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

1 files changed, 23 insertions, 0 deletions

diff --git a/meta/files/common-licenses/GPL-2 b/meta/files/common-licenses/GPL-2
new file mode 100644
index 0000000000..32a4ac68d9
--- /dev/null
+++ b/meta/files/common-licenses/GPL-2
@@ -0,0 +1,23 @@
+
+insert GPL v2 license text here
+
+Linking this library statically or dynamically with other modules is making a
+combined work based on this library. Thus, the terms and conditions of the GNU
+General Public License cover the whole combination.
+
+As a special exception, the copyright holders of this library give you
+permission to link this library with independent modules to produce an
+executable, regardless of the license terms of these independent modules, and
+to copy and distribute the resulting executable under terms of your choice,
+provided that you also meet, for each linked independent module, the terms and
+conditions of the license of that module. An independent module is a module
+which is not derived from or based on this library. If you modify this library,
+you may extend this exception to your version of the library, but you are not
+obligated to do so. If you do not wish to do so, delete this exception
+statement from your version.
+
+
+
+
+
+