From 2c4f7fcc5d3c0856660567aac7489a3a5f8c5343 Mon Sep 17 00:00:00 2001 From: Michał Górny Date: Wed, 28 Nov 2018 10:16:31 +0100 Subject: general-concepts/licenses: Determining the license MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Michał Górny Signed-off-by: Göktürk Yüksek --- general-concepts/licenses/text.xml | 47 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 47 insertions(+) (limited to 'general-concepts') diff --git a/general-concepts/licenses/text.xml b/general-concepts/licenses/text.xml index 093fd9e..f1d5299 100644 --- a/general-concepts/licenses/text.xml +++ b/general-concepts/licenses/text.xml @@ -39,6 +39,53 @@ be used) then use the following syntax: LICENSE="|| ( foo bar )" + +Determining the correct license + + +

+To establish the correct value of LICENSE, you need to trace +the licenses of all installed files. Normally, the licenses of output +files (compiled executables, generated files) are implied +by the licenses of the relevant input files. +

+ +

+When looking for license information, the following should be +considered: +

+ +
    +
  1. + COPYING* and LICENSE* files distributed with + the package +
    2. +
  2. + explicit statements in documentation +
    3. +
  3. + explicit license notices in source and data files +
    4. +
+ +

+The latter (more specific) options take precedence over the former. +In particular, COPYING* files are frequently included as hardcopies +of applicable licenses but the exact application of licenses and their +versions are specified elsewhere. +

+ +

+Please watch for license conflicts. If the license indicated +by the package is incompatible with the licenses used by its sources +(e.g. BSD/MIT package including GPL sources), please contact +the licenses team for guidance. Do not add packages that seem +to include license term violations. +

+ + + + Adding New Licenses -- cgit v1.2.3-65-gdbad