public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
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 11:42:11 +0100	[thread overview]
Message-ID: <20070104114211.0eaabd44@c1358217.kevquinn.com> (raw)
In-Reply-To: <200701031018.58352.pauldv@gentoo.org>

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

On Wed, 3 Jan 2007 10:18:51 +0100
Paul de Vrieze <pauldv@gentoo.org> wrote:

> I know that I'm a bit late on this, but to me the "version 2 or
> later" is a license by itself. Let's call it GPL-RENEW and let the
> file have contents like:
> "This package is licensed with the version x or later clause for the
> GPL."

This is effectively what Diego was proposing with the 'GPL-2+' name.

> The LICENSE would then be:
> LICENSE="GPL-2 GPL-RENEW"
>
> The advantage being that the renew clause is version independent, we
> don't lose information, don't have to mutilate licenses (by adding
> text). If desired it could even be used as LICENSE="|| (GPL-2 GPL-3)
> GPL-RENEW"

This isn't necessary - by creating the 'GPL-2+' license name, the only
thing that's not fully correct as things stand is that packages that
can be accepted with GPL-2 or later won't be accepted if the user has
just GPL-3 in ACCEPT_LICENSES.  Over time this can be fixed, by
replacing "GPL-2" with "GPL-2+" in the LICENSE variable for the
relevant packages.

The the meaning of each license name would be strictly:

GPL-2 : Only licensed under GPL v2
GPL-3 : Only licensed under GPL v3
GPL-2+ : Licensed under GPL v2 or later

Which gives everyone what they need; those wanting GPL-2 or later would
have ACCEPT_LICENSES="GPL-2 GPL-3 GPL-2+".


For me, the only other sane alternative would be to use license groups
(assuming license groups can be specified in the LICENSE variable).  I
don't recall the status of license groups in portage.

-- 
Kevin F. Quinn

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

  parent reply	other threads:[~2007-01-04 10:44 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     ` Kevin F. Quinn [this message]
2007-01-04 11:00       ` [gentoo-dev] " 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
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=20070104114211.0eaabd44@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