Re: new repo layout?

[Ian Campbell <Ian.Campbell@XenSource.com>]

On Mon, 2007-06-04 at 08:39 -0600, Alex Williamson wrote:
> Hi Ian,
> 
>    I see the sparse tree has been removed from staging now.  How do you
> envision architecture maintained trees fit into this new build system?
> For instance, I'd like for a tree cloned from xen-ia64-unstable.hg to
> pull a linux-2.6.18-xen-ia64.hg tree rather than the default upstream
> tree.  I see there's support for cloning linux-2.6.18-xen.hg from a
> directory, but it would be quite an error prone kludge to sneak
> different arch trees in that way.  Thoughts?  Thanks,

Hmm.

xen-unstable will look at a URL derived from it's own parent to find the
Linux tree this means that for the ppc and ia64 trees it will currently
be looking on xenbits for /ext/linux-2.6.18-xen.hg for both archs, this
tree doesn't even exist and I don't think you'll want to share a Linux
tree.

If we define $(XEN_LINUX_ARCH) as "" in the $(XEN_TARGET_ARCH)==x86*
case and -$(XEN_TARGET_ARCH) in != x86 case. Mixing that into
XEN_LINUX_HGREPO would yield /ext/linux-2.6.18-xen-ia64.hg etc. Does
that seem OK to you?

Another option would be to move the ia64 and ppc trees into separate
subdirectories of /ext/. I'm open to other alternatives.

Ian.