public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaran.mccreesh@blueyonder.co.uk>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Ranged licenses
Date: Wed, 28 Nov 2007 23:02:25 +0000	[thread overview]
Message-ID: <20071128230225.2b271b49@blueyonder.co.uk> (raw)
In-Reply-To: <200711282355.01184.bangert@gentoo.org>

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

On Wed, 28 Nov 2007 23:54:57 +0100
Thilo Bangert <bangert@gentoo.org> wrote:
> there is also the legal argument. it's better to state explicitly
> which versions apply and not have to cleanup the mess, when somebody
> decides to release GPL-2.5.

That's an argument strongly in favour of ranged specs. A huge number of
packages are licensed under "GPL 2 or later", and currently most ebuilds
incorrectly use LICENSE="GPL-2" for these. Even changing these to
LICENSE="|| ( GPL-2 GPL-3 )" just shifts the problem around a bit. With
CRAN "GPL 2 or later" translates to "GPL (>= 2)", which is a much more
accurate description of a package's license.

-- 
Ciaran McCreesh

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

  reply	other threads:[~2007-11-28 23:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-24 15:00 [gentoo-dev] Ranged licenses Ciaran McCreesh
2007-11-28 19:06 ` [gentoo-dev] " Christian Faulhammer
2007-11-28 19:11   ` Ciaran McCreesh
2007-11-28 22:54     ` [gentoo-dev] " Thilo Bangert
2007-11-28 23:02       ` Ciaran McCreesh [this message]
2007-11-29  2:19         ` [gentoo-dev] " Ryan Hill
2007-11-29  2:40         ` [gentoo-dev] " Robin H. Johnson
2007-11-29  2:48           ` Ciaran McCreesh
2007-11-29  2:58             ` Robin H. Johnson
2007-11-29  3:04               ` Ciaran McCreesh
2007-11-30 10:04   ` [gentoo-dev] " Steve Long

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=20071128230225.2b271b49@blueyonder.co.uk \
    --to=ciaran.mccreesh@blueyonder.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