From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Adding 'GPL-2-only', 'GPL-3-only' etc. license variants for better auditing
Date: Sat, 21 Sep 2019 21:59:26 +0200 [thread overview]
Message-ID: <44b0c3631c75dcd3aa9230d841796d6be79b7fef.camel@gentoo.org> (raw)
In-Reply-To: <52cf5a0b-4ff4-e238-fea2-7c07908e4ec5@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1022 bytes --]
On Sat, 2019-09-21 at 15:56 -0400, Michael Orlitzky wrote:
> On 9/21/19 12:09 PM, Michał Górny wrote:
> > Hi,
> >
> > TL;DR: I'd like to replace 'GPL-2' with 'GPL-2-only' etc., having
> > the former trigger QA warning asking the dev to double-check if it's
> > 'GPL-2-only' or 'GPL-2+'.
> >
>
> This works only until people start putting
>
> LICENSE="GPL-2-only"
>
> for things that they haven't sufficiently verified.
>
> If we want to let those people keep committing to the tree, then a
> specially-formatted comment might work just as well. It would be harder
> to QA (you'd have to parse the comment and associate it with the
> variable), but it would save us from having to rename the license every
> few years to catch mistakes.
Honestly, do you believe having the choice of 'GPL-2' and 'GPL-2-only'
people would choose the latter without actually checking the difference?
Because the way I see it, choosing the former is much more likely.
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
next prev parent reply other threads:[~2019-09-21 19:59 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 [this message]
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
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=44b0c3631c75dcd3aa9230d841796d6be79b7fef.camel@gentoo.org \
--to=mgorny@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