From: "Haelwenn (lanodan) Monnier" <contact@hacktivis.me>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Should we allow "GPL, v2 or later" for ebuilds?
Date: Thu, 30 Jan 2020 12:20:34 +0100 [thread overview]
Message-ID: <20200130112034.GH16867@cloudsdale.the-delta.net.eu.org> (raw)
In-Reply-To: <w6g4kwhf7o9.fsf@kph.uni-mainz.de>
[2020-01-27 12:41:26+0100] Ulrich Mueller:
> So, the question is, should we allow ebuilds
> # Distributed under the terms of the GNU General Public License, v2 or later
> in the repository, or should we even encourage it for new ebuilds?
>
> I have somewhat mixed feelings about this. One the one hand, I think
> that GPL-2+ should generally be preferred because it offers better
> compatibility. For example, the compatibility clause in CC-BY-SA-4.0
> won't work with GPL-2.
Is there another reason for GPL-2+ than just compatibility?
Because I quite find the "or later" thing to be quite a scary one as
whatever will come up next as a GPL will become applicable and it feels
quite weird to me to have a license that can evolve to whatever
license over time.
I think I would personally slightly prefer to have it be properly
dual-licensed GPL-{2,3} or GPL-2 & CC-BY-SA-4.0 instead.
next prev parent reply other threads:[~2020-01-30 11:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-27 11:41 [gentoo-dev] Should we allow "GPL, v2 or later" for ebuilds? Ulrich Mueller
2020-01-27 11:52 ` Michał Górny
2020-01-27 12:15 ` Jonas Stein
2020-01-27 15:31 ` Rich Freeman
2020-01-30 11:20 ` Haelwenn (lanodan) Monnier [this message]
2020-01-30 13:19 ` Rich Freeman
2020-02-04 0:42 ` Kent Fredric
2020-02-11 15:05 ` Haelwenn (lanodan) Monnier
2020-02-11 15:52 ` Rich Freeman
2020-02-12 4:37 ` Haelwenn (lanodan) Monnier
2020-01-30 13:39 ` Hanno Böck
2020-01-30 14:23 ` Rich Freeman
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=20200130112034.GH16867@cloudsdale.the-delta.net.eu.org \
--to=contact@hacktivis.me \
--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