summaryrefslogtreecommitdiffstats
path: root/meta/files/common-licenses/Artistic-1
diff options
context:
space:
mode:
authorElizabeth Flanagan <elizabeth.flanagan@intel.com>2011-12-03 15:16:15 -0800
committerRichard Purdie <richard.purdie@linuxfoundation.org>2011-12-08 15:24:30 +0000
commitcb91ef9310a2450650ec880be6f0fc3a6e2d4a23 (patch)
tree9886b8bbf81cfb2aedc4825f61ae86c4fae7d2b2 /meta/files/common-licenses/Artistic-1
parentc41b31e45161b16d4a792db208edfaafbc164611 (diff)
downloadpoky-cb91ef9310a2450650ec880be6f0fc3a6e2d4a23.tar.gz
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>
Diffstat (limited to 'meta/files/common-licenses/Artistic-1')
-rw-r--r--meta/files/common-licenses/Artistic-197
1 files changed, 0 insertions, 97 deletions
diff --git a/meta/files/common-licenses/Artistic-1 b/meta/files/common-licenses/Artistic-1
deleted file mode 100644
index 47c9cbdffc..0000000000
--- a/meta/files/common-licenses/Artistic-1
+++ /dev/null
@@ -1,97 +0,0 @@
1
2The Artistic License
3Preamble
4
5The intent of this document is to state the conditions under which a Package
6may be copied, such that the Copyright Holder maintains some semblance of
7artistic control over the development of the package, while giving the users of
8the package the right to use and distribute the Package in a more-or-less
9customary fashion, plus the right to make reasonable modifications.
10
11Definitions:
12
13"Package" refers to the collection of files distributed by the
14Copyright Holder, and derivatives of that collection of files created through
15textual modification.
16"Standard Version" refers to such a Package if it has not been
17modified, or has been modified in accordance with the wishes of the Copyright
18Holder.
19"Copyright Holder" is whoever is named in the copyright or copyrights
20for the package.
21"You" is you, if you're thinking about copying or distributing this
22Package.
23"Reasonable copying fee" is whatever you can justify on the basis of
24media cost, duplication charges, time of people involved, and so on. (You will
25not be required to justify it to the Copyright Holder, but only to the
26computing community at large as a market that must bear the fee.)
27"Freely Available" means that no fee is charged for the item itself,
28though there may be fees involved in handling the item. It also means that
29recipients of the item may redistribute it under the same conditions they
30received it.
311. You may make and give away verbatim copies of the source form of the
32Standard Version of this Package without restriction, provided that you
33duplicate all of the original copyright notices and associated disclaimers.
34
352. You may apply bug fixes, portability fixes and other modifications derived
36from the Public Domain or from the Copyright Holder. A Package modified in such
37a way shall still be considered the Standard Version.
38
393. You may otherwise modify your copy of this Package in any way, provided that
40you insert a prominent notice in each changed file stating how and when you
41changed that file, and provided that you do at least ONE of the following:
42
43a) place your modifications in the Public Domain or otherwise make them Freely
44Available, such as by posting said modifications to Usenet or an equivalent
45medium, or placing the modifications on a major archive site such as
46ftp.uu.net, or by allowing the Copyright Holder to include your modifications
47in the Standard Version of the Package.
48
49b) use the modified Package only within your corporation or organization.
50
51c) rename any non-standard executables so the names do not conflict with
52standard executables, which must also be provided, and provide a separate
53manual page for each non-standard executable that clearly documents how it
54differs from the Standard Version.
55
56d) make other distribution arrangements with the Copyright Holder.
57
584. You may distribute the programs of this Package in object code or executable
59form, provided that you do at least ONE of the following:
60
61a) distribute a Standard Version of the executables and library files, together
62with instructions (in the manual page or equivalent) on where to get the
63Standard Version.
64
65b) accompany the distribution with the machine-readable source of the Package
66with your modifications.
67
68c) accompany any non-standard executables with their corresponding Standard
69Version executables, giving the non-standard executables non-standard names,
70and clearly documenting the differences in manual pages (or equivalent),
71together with instructions on where to get the Standard Version.
72
73d) make other distribution arrangements with the Copyright Holder.
74
755. You may charge a reasonable copying fee for any distribution of this
76Package. You may charge any fee you choose for support of this Package. You may
77not charge a fee for this Package itself. However, you may distribute this
78Package in aggregate with other (possibly commercial) programs as part of a
79larger (possibly commercial) software distribution provided that you do not
80advertise this Package as a product of your own.
81
826. The scripts and library files supplied as input to or produced as output
83from the programs of this Package do not automatically fall under the copyright
84of this Package, but belong to whomever generated them, and may be sold
85commercially, and may be aggregated with this Package.
86
877. C or perl subroutines supplied by you and linked into this Package shall not
88be considered part of this Package.
89
908. The name of the Copyright Holder may not be used to endorse or promote
91products derived from this software without specific prior written permission.
92
939. THIS PACKAGE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR
94IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
95MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE.
96
97The End