From: "Göktürk Yüksek" <gokturk@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: general-concepts/licenses/
Date: Thu, 20 Dec 2018 04:56:01 +0000 (UTC) [thread overview]
Message-ID: <1545281714.0f723044723689a7b05777cb8044558769c3d388.gokturk@gentoo> (raw)
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:
next reply other threads:[~2018-12-20 4:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 4:56 Göktürk Yüksek [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-29 18:36 [gentoo-commits] proj/devmanual:master commit in: general-concepts/licenses/ Ulrich Müller
2023-11-25 13:32 Ulrich Müller
2021-02-13 9:40 Ulrich Müller
2020-05-06 14:29 Ulrich Müller
2020-05-06 14:29 Ulrich Müller
2020-01-14 8:42 Ulrich Müller
2019-12-26 23:53 Göktürk Yüksek
2019-10-16 18:49 Göktürk Yüksek
2019-10-16 18:49 Göktürk Yüksek
2019-09-08 17:55 Ulrich Müller
2018-12-20 4:56 Göktürk Yüksek
2018-12-20 4:56 Göktürk Yüksek
2018-12-20 4:56 Göktürk Yüksek
2018-12-20 4:56 Göktürk Yüksek
2012-10-27 17:48 Markos Chandras
2012-10-27 17:44 Markos Chandras
2012-10-27 17:44 Markos Chandras
2012-10-12 17:44 Ulrich Mueller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1545281714.0f723044723689a7b05777cb8044558769c3d388.gokturk@gentoo \
--to=gokturk@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox