From: "Kevin F. Quinn" <kevquinn@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] GPL-2 vs GPL-2+
Date: Thu, 4 Jan 2007 01:19:45 +0100 [thread overview]
Message-ID: <20070104011945.6f9bc8cf@c1358217.kevquinn.com> (raw)
In-Reply-To: <20061224180548.63e67a11@maya>
[-- Attachment #1: Type: text/plain, Size: 2119 bytes --]
On Sun, 24 Dec 2006 18:05:48 +0000
Stephen Bennett <spb@gentoo.org> wrote:
> On Fri, 22 Dec 2006 21:56:54 +0100
> "Diego 'Flameeyes' Pettenò" <flameeyes@gentoo.org> wrote:
>
> > GPL-2:
> > Note: this license states that the software is licensed under GNU
> > General Public License version 2, and you might not be able to
> > consider it licensed under any later version.
> >
> > GPL-2+:
> > Note: this license explicitly allows licensing under GNU General
> > Public License version 2 or, at your option, any later version.
> >
> > Comments, ideas, proposals?
>
> From a purist point of view, I'd be inclined to go with this route.
> Pragmatically though, given the number of packages that do have the
> "or later" clause compared to the number that don't, it might be
> simpler to split them into GPL-2 (implying "or later") and
> GPL-2-only. That's just a possible naming quibble though -- the idea
> I like.
>
> The suggestion to convert all GPL-2-or-later packages to || ( GPL-2
> GPL-3 ) won't scale -- what happens when GPL-2.1 or GPL-3.1 appear?
> It's also an awful lot of work for something that is, when you get
> down to it, wrong.
I agree. Diego's proposal works fine in practice; the 'might not' in
the description for GPL-2 makes it clear that we don't guarantee to
have updated all existing ebuilds to use the GPL-2+ name where
appropriate.
Doing it on an opportunity basis should be fine, so I don't think we
need to worry about doing GPL-2-only. Saying GPL-2 when GPL-3 is also
acceptable isn't critical in the near term; it won't cause people to
install stuff with a license they don't accept. It won't really be
needed until someone wants to have GPL-3 stuff but no GPL-2-only stuff
- I think it's reasonable to avoid supporting that for a while, at
least. If we start now, with all new commits having GPL-2 changed to
GPL-2+ if appropriate, after a while we can change the GPL-2
description to be GPL-2 only and let GPL-3-only people (there's
always one) bug about packages that are still unchanged when they hit
them.
--
Kevin F. Quinn
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-01-04 0:24 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-22 20:56 [gentoo-dev] GPL-2 vs GPL-2+ Diego 'Flameeyes' Pettenò
2006-12-22 21:53 ` Yuri Vasilevski
2006-12-22 22:06 ` Alec Warner
2006-12-22 22:15 ` Yuri Vasilevski
2006-12-22 22:31 ` Diego 'Flameeyes' Pettenò
2006-12-22 22:43 ` Alec Warner
2006-12-22 23:11 ` Diego 'Flameeyes' Pettenò
2006-12-23 8:40 ` Harald van Dijk
2006-12-22 23:17 ` Yuri Vasilevski
2006-12-23 9:27 ` expose
2007-01-03 9:18 ` Paul de Vrieze
2007-01-03 21:54 ` [gentoo-dev] " Steve Long
2007-01-04 9:17 ` Paul de Vrieze
2007-01-06 17:52 ` [gentoo-dev] " Steve Long
2007-01-06 17:55 ` Steve Long
2007-01-04 10:42 ` [gentoo-dev] " Kevin F. Quinn
2007-01-04 11:00 ` Paul de Vrieze
2007-01-04 13:10 ` Kevin F. Quinn
2007-01-04 17:34 ` Ciaran McCreesh
2006-12-22 23:42 ` [gentoo-dev] " Stefan Schweizer
2006-12-24 18:05 ` [gentoo-dev] " Stephen Bennett
2007-01-04 0:19 ` Kevin F. Quinn [this message]
2007-01-28 0:10 ` [gentoo-dev] " Ryan Hill
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=20070104011945.6f9bc8cf@c1358217.kevquinn.com \
--to=kevquinn@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