diff options
authorMichał Górny <mgorny@gentoo.org>2018-11-28 10:16:31 +0100
committerGöktürk Yüksek <gokturk@gentoo.org>2018-12-19 23:55:21 -0500
commit2c4f7fcc5d3c0856660567aac7489a3a5f8c5343 (patch)
tree7a150b0265bfd1cfbb3979f1da500b17631568c9 /general-concepts
parentgeneral-concepts/licenses: Explain which licenses go into LICENSE (diff)
general-concepts/licenses: Determining the license
Signed-off-by: Michał Górny <mgorny@gentoo.org> Signed-off-by: Göktürk Yüksek <gokturk@gentoo.org>
Diffstat (limited to 'general-concepts')
1 files changed, 47 insertions, 0 deletions
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
@@ -40,6 +40,53 @@ LICENSE="|| ( foo bar )"
+<title>Determining the correct license</title>
+To establish the correct value of <c>LICENSE</c>, 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
+ <li>
+ <c>COPYING*</c> and <c>LICENSE*</c> files distributed with
+ the package
+ </li>
+ <li>
+ explicit statements in documentation
+ </li>
+ <li>
+ explicit license notices in source and data files
+ </li>
+The latter (more specific) options take precedence over the former.
+In particular, <c>COPYING*</c> 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.
<title>Adding New Licenses</title>