All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Stefan Weil <sw@weilnetz.de>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	aliguori@us.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] LICENSE: clarify
Date: Wed, 31 Jul 2013 10:58:26 -0600	[thread overview]
Message-ID: <51F94232.2030009@redhat.com> (raw)
In-Reply-To: <51F93FE0.8040204@weilnetz.de>

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

On 07/31/2013 10:48 AM, Stefan Weil wrote:

>>  
>> -1) QEMU as a whole is released under the GNU General Public License
>> +1) QEMU as a whole is released under the GNU General Public License,
>> +version 2.
> 
> I appreciate these clarifications. For point 1, I suggest
> 
> ... version 2 or (at your option) any later version.
> 
> That is more precise because it excludes "version 2 only"
> and corresponds better to file COPYING.

No.  qemu itself _is_ GPLv2-only, because it uses GPLv2-only code.  That
is, GPLv2-only is the only license compatible with the intersection of
all sources combined together to make the qemu binary.

There are individual files that can (at your option) be upgraded to a
later GPL version, but qemu itself can never be released under GPLv3
without a lot of relicensing work (and likely never to happen, given
that the kernel is the source of some of our GPLv2-only files, and the
kernel is unwilling to use GPLv2+).

[Side note - libvirt ships multiple binaries, where the license on those
binaries differs: libvirt.so is inentionally LGPLv2+; libvirtd is
LGPLv2-only, because that is the only license compatible in the
intersection of libvirt.so and its use of virtualbox code that is
LGPLv2-only; virsh is GPLv3+, because that is the only license
compatible in the intersection of libvirt.so and its use of GPLv3+ readline]

> 
> Maybe we can also refer to the files COPYING and COPYING.LIB.

Yes, that might be worthwhile to do.  (Technically, COPYING.LIB already
refers to COPYING)

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]

  reply	other threads:[~2013-07-31 17:02 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-31  6:19 [Qemu-devel] [PATCH 0/2] Clarify licensing terms Paolo Bonzini
2013-07-31  6:19 ` [Qemu-devel] [PATCH 1/2] raw: add license header Paolo Bonzini
2013-07-31  7:52   ` Kevin Wolf
2013-07-31  8:01   ` Markus Armbruster
2013-08-02  7:01     ` Peter Lieven
2013-07-31 10:49   ` Stefan Hajnoczi
2013-07-31 12:24   ` Jeff Cody
2013-07-31 13:04   ` Luiz Capitulino
2013-08-01  8:13   ` Christoph Hellwig
2013-08-01  8:38     ` Paolo Bonzini
2013-08-15 13:16     ` Anthony Liguori
2013-07-31  6:19 ` [Qemu-devel] [PATCH 2/2] LICENSE: clarify Paolo Bonzini
2013-07-31  7:27   ` Erik de Castro Lopo
2013-07-31  7:40   ` Andreas Färber
2013-07-31 16:48   ` Stefan Weil
2013-07-31 16:58     ` Eric Blake [this message]
2013-08-01  8:29     ` Paolo Bonzini
2013-07-31 17:40   ` Anthony Liguori
2013-08-01  8:21     ` Paolo Bonzini
2014-11-20 19:06   ` Christopher Covington
2013-07-31 15:01 ` [Qemu-devel] [PATCH 0/2] Clarify licensing terms Artyom Tarasenko
2013-08-14 16:29 ` Anthony Liguori

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=51F94232.2030009@redhat.com \
    --to=eblake@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sw@weilnetz.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.