All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Breeds <tony@bakeyournoodle.com>
To: Ewan Mellor <ewan@xensource.com>
Cc: Dan Smith <danms@us.ibm.com>,
	Xen-Devel <xen-devel@lists.xensource.com>,
	XenPPC-devel <xen-ppc-devel@lists.xensource.com>
Subject: Re: [PATCH 0/6][TOOLS][XM-TEST] [v2] Update xm-test to support new architectures
Date: Tue, 3 Oct 2006 06:01:12 +1000	[thread overview]
Message-ID: <20061002200111.GD27551@bakeyournoodle.com> (raw)
In-Reply-To: <20061002150234.GE29149@leeni.uk.xensource.com>

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!

  parent reply	other threads:[~2006-10-02 20:01 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-29  9:56 [PATCH 0/6][TOOLS][XM-TEST] Update xm-test to support new architectures Tony Breeds
2006-09-29  9:56 ` [PATCH 1/6][TOOLS][XM-TEST] Update to use uClib buildroot-snapshot Tony Breeds
2006-09-29  9:56 ` [PATCH 2/6][TOOLS][XM-TEST] Remove hard coded reference to i386 Tony Breeds
2006-09-29  9:56 ` [PATCH 3/6][TOOLS][XM-TEST] rename buildroot -> buildroot-i386 Tony Breeds
2006-09-29  9:56 ` [PATCH 4/6][TOOLS][XM-TEST] Update .hgignore to remove artifacts of ramdisk build Tony Breeds
2006-09-29  9:56 ` [PATCH 5/6][TOOLS][XM-TEST] Refactor code to encapsulate architecture decisions in one place Tony Breeds
2006-09-29  9:57 ` [PATCH 6/6][TOOLS][XM-TEST] Add configuration data for powerpc Tony Breeds
2006-10-01 12:59   ` [XenPPC] " Jimi Xenidis
2006-10-02  5:37     ` Tony Breeds
2006-10-02 10:33       ` Jimi Xenidis
2006-10-02 14:11         ` Dan Smith
2006-10-02 14:43           ` Daniel Stekloff
2006-10-02 12:15 ` [XenPPC] [PATCH 0/6][TOOLS][XM-TEST] [v2] Update xm-test to support new architectures Jimi Xenidis
2006-10-02 12:23 ` Ewan Mellor
2006-10-02 12:40   ` Jimi Xenidis
2006-10-02 14:14   ` Dan Smith
2006-10-02 15:02     ` Ewan Mellor
2006-10-02 15:08       ` [Xen-devel] " Jimi Xenidis
2006-10-02 15:52         ` Ewan Mellor
2006-10-02 20:01       ` Tony Breeds [this message]
2006-10-03 15:20   ` [XenPPC] " Hollis Blanchard
2006-10-03 15:30     ` Ewan Mellor
2006-10-03 15:53       ` Hollis Blanchard
2006-10-03 15:59         ` Keir Fraser
2006-10-03 16:39           ` Aron Griffis
2006-10-03 16:53             ` Keir Fraser
2006-10-02 14:46 ` [PATCH 0/6][TOOLS][XM-TEST] " Daniel Stekloff
2006-10-02 19:52   ` Tony Breeds

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20061002200111.GD27551@bakeyournoodle.com \
    --to=tony@bakeyournoodle.com \
    --cc=danms@us.ibm.com \
    --cc=ewan@xensource.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-ppc-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.