commit: 0f723044723689a7b05777cb8044558769c3d388 Author: Michał Górny <mgorny <AT> gentoo <DOT> org> AuthorDate: Wed Nov 28 09:00:40 2018 +0000 Commit: Göktürk Yüksek <gokturk <AT> gentoo <DOT> org> CommitDate: Thu Dec 20 04:55:14 2018 +0000 URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=0f723044
general-concepts/licenses: Explain which licenses go into LICENSE Explain which licenses go into LICENSE and which don't Signed-off-by: Michał Górny <mgorny <AT> gentoo.org> Signed-off-by: Göktürk Yüksek <gokturk <AT> gentoo.org> general-concepts/licenses/text.xml | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/general-concepts/licenses/text.xml b/general-concepts/licenses/text.xml index 4c4ce62..093fd9e 100644 --- a/general-concepts/licenses/text.xml +++ b/general-concepts/licenses/text.xml @@ -10,6 +10,26 @@ spelling) variable. The license names listed in this variable must match files existing in the repository's <c>licenses/</c> directory. </p> +<p> +The value of this variable should include all licenses pertaining +to the files installed by the package. If some parts of the package +are installed only conditionally, or their license depends on the USE +flag combination, you can use USE conditionals in <c>LICENSE</c>: +</p> + +<codesample lang="ebuild"> +LICENSE="LGPL-2.1+ tools? ( GPL-2+ )" +</codesample> + +<p> +If the package sources include additional files that are not installed, +their license should not be listed. However, if those files are used +at build time, then the license must not impose any restrictions that +could prevent users from building the software. Please also note +that some licenses may impose additional restrictons, e.g. fetch +and/or mirroring restriction. +</p> + <p> If the application is multi-license (either of several licenses can be used) then use the following syntax:
