From: Ulrich Mueller <ulm@gentoo.org>
To: Matt Turner <mattst88@gentoo.org>
Cc: "gentoo development" <gentoo-dev@lists.gentoo.org>,
"Michał Górny" <mgorny@gentoo.org>,
licenses <licenses@gentoo.org>
Subject: Re: [gentoo-dev] Re: [RFC] Adding 'GPL-2-only', 'GPL-3-only' etc. license variants for better auditing
Date: Sun, 22 Sep 2019 01:38:57 +0200 [thread overview]
Message-ID: <w6gy2yhnrse.fsf@kph.uni-mainz.de> (raw)
In-Reply-To: <CAEdQ38Ghd2XYNDAzTWkzwfdtsGOYvvOf7cwBxdugOEaH862XCg@mail.gmail.com> (Matt Turner's message of "Sat, 21 Sep 2019 15:01:38 -0700")
[-- Attachment #1: Type: text/plain, Size: 1374 bytes --]
>>>>> On Sun, 22 Sep 2019, Matt Turner wrote:
> We are all aware. But the point is to explicitly put "-only" in the
> LICENSE metadata so that ebuild authors are less likely to confuse
> GPL-2 vs GPL-2+.
I don't see how renaming could possibly help with that.
>> Plus, it would result in paradoxical entries like "|| ( GPL-2-only
>> GPL-3-only )" for a package that can be distributed under GPL
>> versions 2 or 3 but no later version.
> That paradoxical entry is pretty clear to me.
Not the same thing. "GPL-2-only+" might be clear as well, which doesn't
imply that it isn't paradoxical.
> It's not a one-time audit. Michał has a history of fixing things in
> ways that does not allow the issue to return. I imagine that's what
> he's doing here, and it would not surprise me at all if something
> could be wired into CI to help ensure this.
If it's not a one time audit, it implies that we will permanently have
three variants. This would be a lot of effort, for a tiny gain. After
all, there is absolutely no difference in ACCEPT_LICENSE filtering
between GPL-2 and GPL-2+.
> Trivial concern solved with a news item.
As I've said before, if the intent is to do a tree-wide audit, then
this should be done in a way that has no impact on users. For example,
by adding a comment, instead of changing the LICENSE variable.
Ulrich
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-09-21 23:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-21 16:09 [gentoo-dev] [RFC] Adding 'GPL-2-only', 'GPL-3-only' etc. license variants for better auditing Michał Górny
2019-09-21 16:57 ` Matt Turner
2019-09-21 23:21 ` Matt Turner
2019-09-21 23:46 ` Ulrich Mueller
2019-09-22 0:03 ` Matt Turner
2019-09-24 3:45 ` Matt Turner
2019-09-24 7:13 ` Ulrich Mueller
2019-09-24 15:39 ` Matt Turner
2019-09-21 19:17 ` [gentoo-dev] " Ulrich Mueller
2019-09-21 19:26 ` William Hubbs
2019-09-21 19:57 ` Michał Górny
2019-09-21 22:45 ` William Hubbs
2019-09-22 6:12 ` Michał Górny
2019-09-24 1:42 ` Jason Zaman
2019-09-24 3:43 ` Matt Turner
2019-09-24 6:16 ` Ulrich Mueller
2019-09-21 19:56 ` [gentoo-dev] " Michael Orlitzky
2019-09-21 19:59 ` Michał Górny
2019-09-21 20:02 ` Michael Orlitzky
2019-09-21 20:58 ` [gentoo-dev] " Ulrich Mueller
2019-09-21 22:01 ` Matt Turner
2019-09-21 23:38 ` Ulrich Mueller [this message]
2019-09-22 9:16 ` Kent Fredric
2019-09-22 16:36 ` [gentoo-dev] " Richard Yao
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=w6gy2yhnrse.fsf@kph.uni-mainz.de \
--to=ulm@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=licenses@gentoo.org \
--cc=mattst88@gentoo.org \
--cc=mgorny@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