WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH 0/6][TOOLS][XM-TEST] [v2] Update xm-test to suppo

To: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 0/6][TOOLS][XM-TEST] [v2] Update xm-test to support new architectures
From: Tony Breeds <tony@xxxxxxxxxxxxxxxxxx>
Date: Tue, 3 Oct 2006 06:01:12 +1000
Cc: Dan Smith <danms@xxxxxxxxxx>, Xen-Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, XenPPC-devel <xen-ppc-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 02 Oct 2006 13:01:38 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20061002150234.GE29149@xxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Mail-followup-to: Ewan Mellor <ewan@xxxxxxxxxxxxx>, Dan Smith <danms@xxxxxxxxxx>, Xen-Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, XenPPC-devel <xen-ppc-devel@xxxxxxxxxxxxxxxxxxx>
References: <patchbomb.1159527414@xxxxxxxxxxxxxxxxxxxxxxxxx> <20061002122304.GC29149@xxxxxxxxxxxxxxxxxxxxxx> <m34pumyfdd.fsf@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <20061002150234.GE29149@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Mon, Oct 02, 2006 at 04:02:34PM +0100, Ewan Mellor wrote:
 
> Yes, I think that the best thing to do would be as Jimi suggests, and for us
> to pick one known-good snapshot, and host it ourselves.  That way, the source
> for the XenSource ramdisks will always be available and we don't have to rely
> upon the upstream buildroot archive.
> 
> The next time I build a ramdisk I'll put the buildroot tar on
> xm-test.xensource.com, and change the Makefile to refer to that instead.

What about adding seomthing like:

BT_FILE=buildroot-snapshot
ifdef UCLIB
      BT_SITE="... uclib ..."
else
      BT_SITE="... xensource ..."
endif
BT_URL="$(BT_SITE)/(BT_FILE)"

then have a buildroot-snapshot in xensource somewhere, this allows easy
testing or the upstream snapshots make vs make UCLIB=1, and brace users
automagically end up with a working buildroot if they trying to build
there own ramdisks.

Yours Tony

   linux.conf.au       http://linux.conf.au/ || http://lca2007.linux.org.au/
   Jan 15-20 2007      The Australian Linux Technical Conference!


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>