qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Luke -Jr <luke@dashjr.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU License and proprietary hardware
Date: Fri, 22 Jun 2007 10:21:11 -0500	[thread overview]
Message-ID: <200706221021.11803.luke@dashjr.org> (raw)
In-Reply-To: <265202.13601.qm@web57004.mail.re3.yahoo.com>

On Friday 22 June 2007 00:34, Balazs Attila-Mihaly (Cd-MaN) wrote:
> I must prefix this with the fact that IANAL, but as I understand it, you
> must release the source code only if you distribute that modified system
> (with GPL v2). That is, if you use this system internally in you company,
> you don't have to provide your modifications. But if you, for example,
> provide your clients with the modified version, you have the obligation to
> provide them (your clients, not the Qemu community in general) also with
> the complete source code, after which they have the liberty to redistribute
> the source code under the GPL. 

Correct.

> One solution would be (again, IANAL, so please check with a real lawyer :D),

The solution would be to comply with the GPL and release the code. :)

> is to create an interface to the code you wish to include and put the
> proprietary code in a dynamically linked library which exposes this
> interface. In this case IMHO you have to provide only the code which
> implements the interface in Qemu and loads the shared library, and you would
> have  no obligation regarding the code in the shared library.

The GPL is viral. A derivative-work wrapper would be under the full GPL terms 
and could not link out to a proprietary library either. While there are legal 
loopholes in the GPL, this is not one of them. (and no, I will not provide 
any more info on the loopholes I am aware of)

  reply	other threads:[~2007-06-22 15:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-22  5:34 [Qemu-devel] QEMU License and proprietary hardware Balazs Attila-Mihaly (Cd-MaN)
2007-06-22 15:21 ` Luke -Jr [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-06-21 11:28 Armbrost Failsafe
2007-06-21 22:24 ` Luke -Jr
2007-06-21 22:33   ` M. Warner Losh
2007-06-22 15:18     ` Luke -Jr
2007-06-22 16:07       ` Warner Losh
2007-06-22 16:23         ` Luke -Jr
2007-06-22 16:46           ` M. Warner Losh
2007-06-22 17:11             ` Luke -Jr
2007-06-22 17:30               ` M. Warner Losh
2007-06-22 17:31               ` Ronnie Misra
2007-06-22 17:37               ` Johannes Schindelin
2007-06-22 18:00                 ` Luke -Jr
2007-06-22 18:22                   ` Johannes Schindelin
2007-06-24 20:10 ` Paul Brook

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=200706221021.11803.luke@dashjr.org \
    --to=luke@dashjr.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).