From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:33984) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S5f7c-0006yh-U1 for qemu-devel@nongnu.org; Thu, 08 Mar 2012 10:19:27 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1S5f7Y-00065N-32 for qemu-devel@nongnu.org; Thu, 08 Mar 2012 10:19:16 -0500 Received: from mx1.redhat.com ([209.132.183.28]:15905) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S5f7X-00064J-RT for qemu-devel@nongnu.org; Thu, 08 Mar 2012 10:19:12 -0500 Message-ID: <4F58CDEA.2020506@redhat.com> Date: Thu, 08 Mar 2012 12:19:06 -0300 From: Lucas Meneghel Rodrigues MIME-Version: 1.0 References: <4F582EDB.1040608@redhat.com> <4F58B5CB.8040503@codemonkey.ws> In-Reply-To: <4F58B5CB.8040503@codemonkey.ws> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC] Future goals for autotest and virtualization tests List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Cleber Rosa , QEMU devel , Ademar Reis Before I forget, I'd like to ask you about this: On 03/08/2012 10:36 AM, Anthony Liguori wrote: > I'm really not a fan of buildroot. Note that in order to ship binaries, > full source needs to be provided in order to comply with the GPL. The > FSF at least states that referring to another website for source that's > not under your control doesn't satisfy the requirements of the GPL. About using buildroot, what is up with it, since it is mature and works well? You mentioned than providing all the sources is harder than it looks like, and I surely think this might be the case. But in all my naiveness, if the problem is to ship the exact source with the images have been built, couldn't I just ask buildroot to fetch all the tarball sources (there's a function to perform source download only) and add them to the appropriate git branch? Granted, it sounds horribly inefficient space wise, but wouldn't it solve the requirements? Anyone can uncompress tarballs and see the source there. I've built the images using the latest release tarballs of each project, such as linux, uclibc, busybox and such. I wanted something up to date enough (example, linux 3.2.6) but not downright git master HEAD, since lots of problems can creep up by doing it.