public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: Jason Zaman <perfinion@gentoo.org>
Cc: 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: Tue, 24 Sep 2019 08:16:34 +0200	[thread overview]
Message-ID: <w6g36gmnrr1.fsf@kph.uni-mainz.de> (raw)
In-Reply-To: <20190924014220.GA45747@baraddur.perfinion.com> (Jason Zaman's message of "Tue, 24 Sep 2019 09:42:20 +0800")

[-- Attachment #1: Type: text/plain, Size: 1025 bytes --]

>>>>> On Tue, 24 Sep 2019, Jason Zaman wrote:

> The "GPL-2.0" one is deprecated:
> https://spdx.org/licenses/GPL-2.0.html

> If SPDX moved to having two names "-only" and "-or-later" then we
> should too.

The main problem is that we will always have licenses that are not in
their list. So if they add them later, chances are that we would have to
rename ours, forcing our users to update their ACCEPT_LICENSE variable
and possibly reinstall packages.

Generally, it is also not predictable what they will choose as an
identifier. For example, there is "BSD-2-Clause" but "0BSD". Sometimes
they stick with the upstream version (e.g. CDDL-1.0), sometimes they
invent their own (GPL-2.0-only), and sometimes they drop the version
altogether (WTFPL). In addition, they change their names, which would
make it even more difficult to catch up.

So, we can use SPDX as a guideline when adding _new_ licenses, but I
don't see any good reason for renaming existing ones. Especially when
the SPDX identifiers aren't stable.

Ulrich

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  parent reply	other threads:[~2019-09-24  6:16 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 [this message]
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
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=w6g36gmnrr1.fsf@kph.uni-mainz.de \
    --to=ulm@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=licenses@gentoo.org \
    --cc=mgorny@gentoo.org \
    --cc=perfinion@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