From: Jamie Lokier <jamie@shareable.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Binary package and the kqemu support.
Date: Wed, 10 Aug 2005 13:56:38 +0100 [thread overview]
Message-ID: <20050810125638.GB22753@mail.shareable.org> (raw)
In-Reply-To: <200508091702.39938.paul@codesourcery.com>
Paul Brook wrote:
> > From http://fabrice.bellard.free.fr/qemu/qemu-accel.html:
> >
> > Terms of Use
> > The QEMU Accelerator is free to use, but it is a closed source
> > proprietary product. You are not allowed to distribute it yourself to
> > other people without an explicit authorisation. Distributors wishing to
> > include the QEMU accelerator on CDs, ISO images or packages must contact
> > the author to know the exact terms.
>
> However the qemu 0.7.1 binaries distributed from the qemu website include
> kqemu support. This means you are entitled to kqemu.h (which is
> necessary to compile kqemu.c) under the LGPL.
No, that is not correct.
> By distributing kqemu enabled qemu binaries Fabrice has implicitly
> dual-licenced kqemu.h under both the LGPL and his kqemu proprietary licence.
No.
Fabrice is special, because he is the copyright holder. He has the
right to distribute binaries, prepared using his own source, using
whatever license he likes.
That by itself does _not_ grant you an "implicit" license to the
source used to prepare those binaries.
However, if he is distributing _source_ for kqemu-enabled qemu
including kqemu.h, and if he states that the whole source tarball
(which happened to include kqemu.h) is under the LGPL, then you could
begin to make a case for an implied license of parts of the tarball
(i.e. kqemu.h, if it's in that source tarball). I don't know if he's
doing that.
Also, if he is distributing binaries where part of the binary is
LGPL'd or GPL'd code where the _copyright is held by other people_
(i.e. contributors), then you can make a case that if he's
distributing kqemu-enabled binaries of qemu (that nobody else is able
to legally reproduce), he's infringing the contributor's copyright.
But if he's only distributed binaries which are compiled from _his_
LGPL'd code and _his_ closed source code - well, he can simply do
that, and the binaries come under whatever binary license he's using.
This is all moot, however, as you can just ask Fabrice and he may well
be happy to put kqemu.h under the same license as qemu.
It's only a small interface file, and nearly all of it, or perhaps all
of it (these things are uncertain), may be usable under fair use anyway.
-- Jamie
next prev parent reply other threads:[~2005-08-10 13:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-09 10:24 [Qemu-devel] Binary package and the kqemu support Piotr Roszatycki
2005-08-09 10:49 ` Adrian Smarzewski
2005-08-09 10:50 ` Adrian Smarzewski
2005-08-09 14:20 ` Johannes Schindelin
2005-08-09 15:17 ` Henrik Nordstrom
2005-08-09 15:36 ` Thomas Petazzoni
2005-08-09 16:02 ` Paul Brook
2005-08-09 21:14 ` Adrian Smarzewski
2005-08-10 12:56 ` Jamie Lokier [this message]
2005-08-10 13:15 ` Paul Brook
2005-08-09 18:59 ` Fabrice Bellard
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=20050810125638.GB22753@mail.shareable.org \
--to=jamie@shareable.org \
--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).