public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Yuri Vasilevski <yvasilev@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] GPL-2 vs GPL-2+
Date: Fri, 22 Dec 2006 17:17:07 -0600	[thread overview]
Message-ID: <20061222171707.54b060fe@dukebook.lan> (raw)
In-Reply-To: <200612222331.17989@enterprise.flameeyes.is-a-geek.org>

On Fri, 22 Dec 2006 23:31:04 +0100
"Diego 'Flameeyes' Pettenò" <flameeyes@gentoo.org> wrote:

> On Friday 22 December 2006 22:53, Yuri Vasilevski wrote:
> > 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"
> >
> > when it becomes available?
> There is one problem at least for this: to apply this method you'd
> have to change _all_ the ebuilds in the tree referring to GPL-2 or
> later when GPL-3 is published, while with GPL-2+ we can start
> gradually now.

Yes, this will require us to update ebuils once in like 5 (or 15?)
years to catch with FSF. But at the benefit of having less confusion
for users about "What the heck is a GPL-2+?" for at last the same period
of time.

GPL-2 is not a licence nor it is not a standard notation for that way
of having multilicencing. So users will have to check what's the
meaning of that + at the end of GPL-2+, so I think it'll create much
more confusion than the work of updating packages with each new version
of GPL.

Also there could be a case that softer v3 is out, FSF will rethink and
come up with something acceptable to Linus (and other people that
refuse to migrate), as (as far as I can understand) GPL-3 will not be
compatible with GPL-2. So there could be the case of having a package
licenced under GPL-2, GPL-2.1 or later. (This is just an example, I
actually have no idea whatever this will be the case of having a softer
GPL-3.x.)

> Also it would be more useful for users to know what can be licensed
> in 2+ and what requires 2 strictly.

This info can be easily and automatically extracted from LICENSE
variable by applying some boolean logic ;-)

Yuri.

-- 
gentoo-dev@gentoo.org mailing list



  parent reply	other threads:[~2006-12-22 23:20 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 [this message]
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
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=20061222171707.54b060fe@dukebook.lan \
    --to=yvasilev@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