public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Paul de Vrieze <pauldv@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] GPL-2 vs GPL-2+
Date: Wed, 3 Jan 2007 10:18:51 +0100	[thread overview]
Message-ID: <200701031018.58352.pauldv@gentoo.org> (raw)
In-Reply-To: <20061222155325.0f97c017@dukebook.lan>

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

On Friday 22 December 2006 22:53, Yuri Vasilevski wrote:
> Hi,
>
> On Fri, 22 Dec 2006 21:56:54 +0100
>
> "Diego 'Flameeyes' Pettenò" <flameeyes@gentoo.org> wrote:
> > At the moment we represent the software we consider under GNU General
> > Public License, version 2 of the license, but we cannot be sure it's
> > alright to license it to "any later version". Linux kernel for
> > instance is licensed _only_ under GPLv2, but not any later version.
>
> I don't think this is a good solution, as in any case the package is
> licensed under GPL-2, so how about for the packages that only support
> GPL-2 we set:
>
> LICENSE="GPL-2"
>
> While for the ones that support v2 or later (this is actually a special
> case of multiple licensing) we do:
>
> LICENSE="GPL-2 GPL-3"

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."

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"

Paul

-- 
Paul de Vrieze
Gentoo Developer
Mail: pauldv@gentoo.org
Homepage: http://www.devrieze.net

[-- Attachment #2: Type: application/pgp-signature, Size: 185 bytes --]

  parent reply	other threads:[~2007-01-03  9:22 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 [this message]
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
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=200701031018.58352.pauldv@gentoo.org \
    --to=pauldv@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