From: Steve Long <slong@rathaus.eclipse.co.uk>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: GPL-2 vs GPL-2+
Date: Wed, 03 Jan 2007 21:54:07 +0000 [thread overview]
Message-ID: <enh8i1$7hh$1@sea.gmane.org> (raw)
In-Reply-To: 200701031018.58352.pauldv@gentoo.org
Paul de Vrieze 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."
>
> 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"
>
That last bit's excessive IMO. It seems to add complexity- does it mean you
can have either of the GPL2 or 3 plus any later from that version? Why not
just cover that with your first example, which I like a lot- it spells out
the later clause, and as you say, is version-independent.
So GPL-3 GPL-RENEW could be specified, as well as simple GPL-2, or GPL-2
GPL-RENEW. (Just spelling it out, sorry.)
I'm thinking about your example and I can see how it covers a user who
*wants* to use GPL-3 (eg for their own code) but I still think that comes
under GPL-2 GPL-RENEW as it's clearly allowed.
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2007-01-03 21:58 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 ` Steve Long [this message]
2007-01-04 9:17 ` [gentoo-dev] " 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='enh8i1$7hh$1@sea.gmane.org' \
--to=slong@rathaus.eclipse.co.uk \
--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