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: <1545281730.4aee878793ba33740866cc763f341db5531cbf09.gokturk@gentoo> (raw)
commit: 4aee878793ba33740866cc763f341db5531cbf09
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Wed Nov 28 09:23:45 2018 +0000
Commit: Göktürk Yüksek <gokturk <AT> gentoo <DOT> org>
CommitDate: Thu Dec 20 04:55:30 2018 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=4aee8787
general-concepts/licenses: Warn about GPL-n+ etc.
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 | 28 ++++++++++++++++++++++++++++
1 file changed, 28 insertions(+)
diff --git a/general-concepts/licenses/text.xml b/general-concepts/licenses/text.xml
index f1d5299..aa2ca74 100644
--- a/general-concepts/licenses/text.xml
+++ b/general-concepts/licenses/text.xml
@@ -86,6 +86,34 @@ to include license term violations.
</body>
</subsection>
+<subsection>
+<title>GPL-x vs GPL-x+</title>
+<body>
+
+<p>
+FSF licenses (GPL, LGPL, AGPL, FDL) occur in two variants: the 'vN only'
+and 'vN or later' variants. In Gentoo, the licenses of the latter variants
+are denoted by appending
+a plus sign (+) to their respective license notations of the former variant,
+e.g. <c>GPL-2+</c> and <c>GPL-2</c>.
+</p>
+
+<p>
+Determining the correct variant usually requires looking for copyright
+notices in the code. For example, the following copyright notice
+indicates <c>GPL-2+</c> license:
+</p>
+
+<pre>
+ * This program is free software; you can redistribute it and/or
+ * modify it under the terms of the GNU General Public License as
+ * published by the Free Software Foundation; either version 2 of
+ * the License, or (at your option) any later version.
+</pre>
+
+</body>
+</subsection>
+
<subsection>
<title>Adding New Licenses</title>
<body>
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=1545281730.4aee878793ba33740866cc763f341db5531cbf09.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