From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D7p5i-000085-Fe for qemu-devel@nongnu.org; Sun, 06 Mar 2005 01:18:15 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D7p5X-0008Vh-94 for qemu-devel@nongnu.org; Sun, 06 Mar 2005 01:18:07 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D7p5V-0008Rl-Fk for qemu-devel@nongnu.org; Sun, 06 Mar 2005 01:18:01 -0500 Received: from [216.58.162.138] (helo=netraverse.com) by monty-python.gnu.org with esmtp (SSLv3:DES-CBC3-SHA:168) (Exim 4.34) id 1D7oVP-0006Zh-7q for qemu-devel@nongnu.org; Sun, 06 Mar 2005 00:40:43 -0500 Received: from [69.165.224.96] (account lreiter HELO [10.1.0.1]) by netraverse.com (CommuniGate Pro SMTP 4.0.5) with ESMTP-TLS id 4679646 for qemu-devel@nongnu.org; Sat, 05 Mar 2005 21:59:56 -0700 Message-ID: <422A97C9.5090004@win4lin.com> Date: Sun, 06 Mar 2005 00:40:25 -0500 From: "Leonardo E. Reiter" MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: Sponsorship for QEMU Developers... References: <4228C0D9.8000601@win4lin.com> <200503051413.36906.os2@videotron.ca> <422A325B.1090301@win4lin.com> <422A6F69.30808@win4lin.com> <1110079971.1913.931.camel@aragorn> <20050306034737.GA11680@jbrown.mylinuxbox.org> <1110083839.12889.5.camel@aragorn> In-Reply-To: <1110083839.12889.5.camel@aragorn> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Hi John, I apologize for any confusion. In fact I think I also used 'GPL' in my note by mistake instead of 'LGPL'. The bottom line is just that we always prefer to err on the safe side, thus we chose not to include files such as 'vl.h' in our closed source bits. Plus, it can get a bit dicey when the same tarball actually contains code with 2 or 3 (most files have BSD-style licenses in their comment headers!) types of licenses. It was just the safe thing to do from our perspective, even if we were not even enabling the GPL'd code. If you or anyone else has any other questions about how we interact with QEMU in our Win4Lin Pro product, please ask. I want to be as honest and forward as possible with everyone, and hope that my company can work together in harmony with this great QEMU community. Thank you for your understanding, Leo Reiter John R. Hogerhuis wrote: > > Color me confused, but Leo made the point that he is avoiding including > any header files and instead dynamically linking. Why bother if the > pieces in question are LGPLed or even better for him BSD'ed? Talk of > code "contamination," etc. > -- Leonardo E. Reiter Vice President of Engineering Win4Lin, Inc. Virtual Computing from Desktop to Data Center Main: +1 512 339 7979 Fax: +1 512 532 6501 http://www.win4lin.com