From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:46007) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S5iWj-000331-I6 for qemu-devel@nongnu.org; Thu, 08 Mar 2012 13:57:26 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1S5iWh-0007q7-MC for qemu-devel@nongnu.org; Thu, 08 Mar 2012 13:57:25 -0500 Received: from mail-pz0-f45.google.com ([209.85.210.45]:54059) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S5iWh-0007pl-Fd for qemu-devel@nongnu.org; Thu, 08 Mar 2012 13:57:23 -0500 Received: by dadp14 with SMTP id p14so840324dad.4 for ; Thu, 08 Mar 2012 10:57:20 -0800 (PST) Message-ID: <4F59010C.2060105@codemonkey.ws> Date: Thu, 08 Mar 2012 12:57:16 -0600 From: Anthony Liguori MIME-Version: 1.0 References: <4F582EDB.1040608@redhat.com> <4F58B5CB.8040503@codemonkey.ws> <4F58CDEA.2020506@redhat.com> In-Reply-To: <4F58CDEA.2020506@redhat.com> 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: Lucas Meneghel Rodrigues Cc: Ademar Reis , QEMU devel , Cleber Rosa On 03/08/2012 09:19 AM, Lucas Meneghel Rodrigues wrote: > 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. buildroot is a full blown distribution. But instead of distributing binaries, it only distributes source code. Think of it like Gentoo--. It relies on third party links to fetch said source code which means that it's not unusual at all for buildroot to straight out fail. Because it needs a GCC that can build shared libraries, it also requires rebuilding GCC which increases the build time even for a minimalistic configuration. Having a JeOS it not meant to replace having proper guests (like Fedora or Ubuntu). As I've said in other notes, the point of having a JeOS is to essentially use Linux as a libOS when writing unit tests. > 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? Okay, let's say I'm a developer and I want to use a new Linux kernel to test the new virtio-pci feature I added with buildroot. Where do I begin? What patch do I submit? That's the use case I'm trying to go after. Regards, Anthony Liguori