From 558b5043e1d5a36caff137093fd04abcf025af1c Mon Sep 17 00:00:00 2001 From: Elizabeth Flanagan Date: Sat, 3 Dec 2011 15:16:15 -0800 Subject: [YOCTO #1776] 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. Signed-off-by: Elizabeth Flanagan --- meta/files/common-licenses/QPL-1 | 96 ---------------------------------------- 1 file changed, 96 deletions(-) delete mode 100644 meta/files/common-licenses/QPL-1 (limited to 'meta/files/common-licenses/QPL-1') diff --git a/meta/files/common-licenses/QPL-1 b/meta/files/common-licenses/QPL-1 deleted file mode 100644 index ec61bd690..000000000 --- a/meta/files/common-licenses/QPL-1 +++ /dev/null @@ -1,96 +0,0 @@ - -THE Q PUBLIC LICENSE version 1.0 - -Copyright (C) 1999-2005 Trolltech AS, Norway. -Everyone is permitted to copy and distribute this license document. -The intent of this license is to establish freedom to share and change the -software regulated by this license under the open source model. - -This license applies to any software containing a notice placed by the -copyright holder saying that it may be distributed under the terms of the Q -Public License version 1.0. Such software is herein referred to as the -Software. This license covers modification and distribution of the Software, -use of third-party application programs based on the Software, and development -of free software which uses the Software. - -Granted Rights - -1. You are granted the non-exclusive rights set forth in this license provided -you agree to and comply with any and all conditions in this license. Whole or -partial distribution of the Software, or software items that link with the -Software, in any form signifies acceptance of this license. - -2. You may copy and distribute the Software in unmodified form provided that -the entire package, including - but not restricted to - copyright, trademark -notices and disclaimers, as released by the initial developer of the Software, -is distributed. - -3. You may make modifications to the Software and distribute your -modifications, in a form that is separate from the Software, such as patches. -The following restrictions apply to modifications: - -a. Modifications must not alter or remove any copyright notices in the -Software. -b. When modifications to the Software are released under this license, a non- -exclusive royalty-free right is granted to the initial developer of the -Software to distribute your modification in future versions of the Software -provided such versions remain available under these terms in addition to any -other license(s) of the initial developer. - -4. You may distribute machine-executable forms of the Software or machine- -executable forms of modified versions of the Software, provided that you meet -these restrictions: - -a. You must include this license document in the distribution. -b. You must ensure that all recipients of the machine-executable forms are also -able to receive the complete machine-readable source code to the distributed -Software, including all modifications, without any charge beyond the costs of -data transfer, and place prominent notices in the distribution explaining this. - -c. You must ensure that all modifications included in the machine-executable -forms are available under the terms of this license. - -5. You may use the original or modified versions of the Software to compile, -link and run application programs legally developed by you or by others. - -6. You may develop application programs, reusable components and other software -items that link with the original or modified versions of the Software. These -items, when distributed, are subject to the following requirements: - -a. You must ensure that all recipients of machine-executable forms of these -items are also able to receive and use the complete machine-readable source -code to the items without any charge beyond the costs of data transfer. -b. You must explicitly license all recipients of your items to use and re- -distribute original and modified versions of the items in both machine- -executable and source code forms. The recipients must be able to do so without -any charges whatsoever, and they must be able to re-distribute to anyone they -choose. - -c. If the items are not available to the general public, and the initial -developer of the Software requests a copy of the items, then you must supply -one. - -Limitations of Liability - -In no event shall the initial developers or copyright holders be liable for any -damages whatsoever, including - but not restricted to - lost revenue or profits -or other direct, indirect, special, incidental or consequential damages, even -if they have been advised of the possibility of such damages, except to the -extent invariable law, if any, provides otherwise. - -No Warranty - -The Software and this license document are provided AS IS with NO WARRANTY OF -ANY KIND, INCLUDING THE WARRANTY OF DESIGN, MERCHANTABILITY AND FITNESS FOR A -PARTICULAR PURPOSE. - -Choice of Law - -This license is governed by the Laws of Norway. Disputes shall be settled by -Oslo City Court. - - - - - - -- cgit v1.2.3