From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Add support for new image type
Date: Thu, 01 Mar 2012 21:38:24 +0100 [thread overview]
Message-ID: <jiomo2$mfc$1@dough.gmane.org> (raw)
In-Reply-To: <4F4FDB8A.6060507@storagecraft.com>
Il 01/03/2012 21:26, Kai Meyer ha scritto:
>> QEMU uses GPL v2. You can use a patched QEMU internally,
>> but as soon as you want to give it to customers (or get it integrated
>> in the official source tree), you must publish all code which is needed
>> under an open license.
>
> It is a shared library.
>
>> If your image access library is a shared library (linked at runtime),
>> the situation is more difficult. The intention of the GPL is still
>> that you have to publish your code (this is also what the FSF says),
>> but there are different opinions for GPL v2.
There aren't really different opinions. Some people *tolerate*
proprietary plugins, but strictly speaking that should be done with a
specific exception to the GPL. It is not "some people think it's legal,
some people don't". It is more like "some people don't care, some
people do".
> http://wiki.qemu.org/License
> Portions of qemu (ie the qed block driver) are licensed under the LGPL.
> Can you help me understand the impact of licensing our contributions
> under the LGPL instead of GPL?
No. The LGPL parts are separate, but when you distribute the
combination you still have to honor _all_ the licenses at the same time.
In practice this means the most restrictive license, which is the GPL.
Paolo
next prev parent reply other threads:[~2012-03-01 20:38 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 21:52 [Qemu-devel] Add support for new image type Kai Meyer
2012-03-01 0:16 ` Brian Jackson
2012-03-01 15:03 ` Kevin Wolf
2012-03-01 19:45 ` Kai Meyer
2012-03-01 20:10 ` Stefan Weil
2012-03-01 20:18 ` Stefan Weil
2012-03-01 20:31 ` Kai Meyer
2012-03-01 21:05 ` Anthony Liguori
2012-03-01 21:14 ` Kai Meyer
2012-03-02 6:54 ` Paolo Bonzini
2012-03-02 18:38 ` Kai Meyer
2012-03-05 9:14 ` Paolo Bonzini
2012-03-05 12:14 ` Stefan Hajnoczi
2012-05-16 17:06 ` Kai Meyer
2012-05-16 17:48 ` Paolo Bonzini
2012-05-16 18:21 ` Anthony Liguori
2012-05-16 18:56 ` Kai Meyer
2012-05-16 19:20 ` Kai Meyer
2012-05-17 9:10 ` Artyom Tarasenko
2012-05-17 9:41 ` Paolo Bonzini
2012-05-17 11:03 ` Artyom Tarasenko
2012-05-17 17:53 ` Kai Meyer
2012-05-17 19:43 ` Paolo Bonzini
2012-05-17 20:18 ` Kai Meyer
2012-03-01 20:26 ` Kai Meyer
2012-03-01 20:38 ` Paolo Bonzini [this message]
2012-03-01 20:53 ` Stefan Weil
2012-03-01 21:02 ` Anthony Liguori
2012-03-08 15:17 ` Kevin Wolf
2012-03-08 17:16 ` Nate Bushman
2012-03-09 9:23 ` Kevin Wolf
2012-03-09 10:28 ` Paolo Bonzini
2012-03-09 11:26 ` Kevin Wolf
2012-03-10 16:54 ` Nate Bushman
2012-03-10 16:53 ` Nate Bushman
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='jiomo2$mfc$1@dough.gmane.org' \
--to=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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 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.