From: Jamie Lokier <jamie@shareable.org>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel <qemu-devel@nongnu.org>,
Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] QLicense chaos
Date: Sat, 8 May 2010 00:02:34 +0100 [thread overview]
Message-ID: <20100507230233.GA7836@shareable.org> (raw)
In-Reply-To: <4BE46C8A.2010002@web.de>
Jan Kiszka wrote:
> Moreover, some of the QObject files are LGPL, some GPL. I bet this was
> also not intended. But what was the idea behind the LGPL? Some libqmp which
> can be used by closed source apps?
I believe LGPL is needed for source apps that have GPLv2-incompatible
licensing. E.g. GPLv3, Apache license, OpenSSL? (I'm not sure exactly.)
And for those who want to keep their own apps BSD-like.
-- Jamie
next prev parent reply other threads:[~2010-05-07 23:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-07 19:39 [Qemu-devel] QLicense chaos Jan Kiszka
2010-05-07 19:56 ` [Qemu-devel] " Luiz Capitulino
2010-05-07 23:02 ` Jamie Lokier [this message]
2010-05-08 0:05 ` [Qemu-devel] " 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=20100507230233.GA7836@shareable.org \
--to=jamie@shareable.org \
--cc=aliguori@us.ibm.com \
--cc=jan.kiszka@web.de \
--cc=lcapitulino@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).