From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:53654) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RFo0Q-0006D4-LW for qemu-devel@nongnu.org; Mon, 17 Oct 2011 10:17:31 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RFo0P-0006am-JI for qemu-devel@nongnu.org; Mon, 17 Oct 2011 10:17:30 -0400 Received: from mail-gy0-f173.google.com ([209.85.160.173]:48374) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RFo0P-0006ag-Gq for qemu-devel@nongnu.org; Mon, 17 Oct 2011 10:17:29 -0400 Received: by gyg10 with SMTP id 10so3759041gyg.4 for ; Mon, 17 Oct 2011 07:17:29 -0700 (PDT) Message-ID: <4E9C38F5.2060803@codemonkey.ws> Date: Mon, 17 Oct 2011 09:17:25 -0500 From: Anthony Liguori MIME-Version: 1.0 References: <1318213565-3268-1-git-send-email-jcmvbkbc@gmail.com> <1318213565-3268-7-git-send-email-jcmvbkbc@gmail.com> <4E9C0746.3030509@suse.de> <4E9C21C0.5070102@us.ibm.com> <4E9C249D.3080509@redhat.com> In-Reply-To: <4E9C249D.3080509@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] GPLv3 troubles List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: Anthony Liguori , qemu-devel@nongnu.org, Blue Swirl , Max Filippov , Avi Kivity , =?ISO-8859-1?Q?Andreas_F=E4rber?= On 10/17/2011 07:50 AM, Paolo Bonzini wrote: > On 10/17/2011 02:38 PM, Anthony Liguori wrote: >>> Could we please draft some policy on this? This is not a GDB issue, it's >>> very general. Whether we like it or not, there is GPLv3-licensed code >>> and there will probably be a GPLv4 one day. >> >> I don't see anything wrong with GPLv2 only. While I don't think there's >> anything wrong with GPLv3, I think that "or later" is a dangerous clause >> to add. > > License fragmentation with respect to the de facto standard toolchain (binutils) > is wrong. Fragmentation with respect to the de factor standard kernel (Linux) is wrong. We currently pull in code (mostly headers, although not exclusively) from Linux too. That puts us between a rock and a hard place. Regards, Anthony Liguori > Until llvm includes support for as many obscure targets as we support > in QEMU, some level of pragmatism might be necessary. > > Paolo >