From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: quickstart/
Date: Mon, 13 May 2019 18:52:10 +0000 (UTC) [thread overview]
Message-ID: <1557773409.11a85f9596d71521a8018faf4d73d730d163187a.ulm@gentoo> (raw)
commit: 11a85f9596d71521a8018faf4d73d730d163187a
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Mon Apr 22 07:14:20 2019 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Mon May 13 18:50:09 2019 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=11a85f95
quickstart: Correct LICENSE in ebuild snippets
While there's no real reason for those snippets to be correct, I think
it'd be generally beneficial to show developers that the '+' license
variants do exist and are quite common.
Signed-off-by: Michał Górny <mgorny <AT> gentoo.org>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
quickstart/text.xml | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/quickstart/text.xml b/quickstart/text.xml
index e47433e..5a33ead 100644
--- a/quickstart/text.xml
+++ b/quickstart/text.xml
@@ -43,7 +43,7 @@ DESCRIPTION="Exuberant ctags generates tags files for quick source navigation"
HOMEPAGE="http://ctags.sourceforge.net"
SRC_URI="mirror://sourceforge/ctags/${P}.tar.gz"
-LICENSE="GPL-2"
+LICENSE="GPL-2+"
SLOT="0"
KEYWORDS="~mips ~sparc ~x86"
@@ -111,7 +111,8 @@ name and version <d/> in this case, it would be <c>ctags-5.5.4</c>.
</p>
<p>
-The <c>LICENSE</c> is <c>GPL-2</c> (the GNU General Public License version 2).
+The <c>LICENSE</c> is <c>GPL-2+</c> (the GNU General Public License version 2
+or (at your option) any later version).
</p>
<p>
@@ -333,7 +334,7 @@ DESCRIPTION="GNU charset conversion library for libc which doesn't implement it"
HOMEPAGE="https://www.gnu.org/software/libiconv/"
SRC_URI="ftp://ftp.gnu.org/pub/gnu/libiconv/${P}.tar.gz"
-LICENSE="LGPL-2.1"
+LICENSE="LGPL-2+ GPL-3+"
SLOT="0"
KEYWORDS="~amd64 ~ppc ~sparc ~x86"
IUSE="nls"
@@ -378,7 +379,7 @@ DESCRIPTION="A lightweight email client and newsreader"
HOMEPAGE="https://sylpheed.good-day.net/"
SRC_URI="mirror://sourceforge/${PN}/${P}.tar.bz2"
-LICENSE="GPL-2"
+LICENSE="GPL-2+ LGPL-2.1+"
SLOT="0"
KEYWORDS="alpha amd64 hppa ia64 ppc ppc64 sparc x86"
IUSE="crypt imlib ipv6 ldap nls pda ssl xface"
next reply other threads:[~2019-05-13 18:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 18:52 Ulrich Müller [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-18 2:07 [gentoo-commits] proj/devmanual:master commit in: quickstart/ Sam James
2022-03-13 1:47 Sam James
2021-12-09 4:12 Sam James
2021-12-09 4:09 Sam James
2021-12-09 4:08 Sam James
2021-12-09 4:08 Sam James
2020-02-16 18:05 Ulrich Müller
2020-01-23 13:50 Ulrich Müller
2019-11-26 3:05 Göktürk Yüksek
2019-11-26 1:49 Göktürk Yüksek
2019-05-13 18:52 Ulrich Müller
2019-05-13 18:52 Ulrich Müller
2018-10-24 17:49 Brian Evans
2018-06-14 18:43 Göktürk Yüksek
2016-10-28 14:41 Göktürk Yüksek
2015-08-09 12:39 Justin Lecher
2015-08-09 12:39 Justin Lecher
2013-01-21 8:18 Pacho Ramos
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=1557773409.11a85f9596d71521a8018faf4d73d730d163187a.ulm@gentoo \
--to=ulm@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