|author||Michał Górny <email@example.com>||2018-11-28 10:00:40 +0100|
|committer||Göktürk Yüksek <firstname.lastname@example.org>||2018-12-19 23:55:14 -0500|
|parent||general-concepts/licenses: make it clear that multiple can be listed (diff)|
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 <email@example.com> Signed-off-by: Göktürk Yüksek <firstname.lastname@example.org>
Diffstat (limited to 'general-concepts')
1 files changed, 20 insertions, 0 deletions
diff --git a/general-concepts/licenses/text.xml b/general-concepts/licenses/text.xml
index 4c4ce62..093fd9e 100644
@@ -11,6 +11,26 @@ match files existing in the repository's <c>licenses/</c> directory.
+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>:
+LICENSE="LGPL-2.1+ tools? ( GPL-2+ )"
+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.
If the application is multi-license (either of several licenses can
be used) then use the following syntax: