From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: new repo layout? Date: Mon, 04 Jun 2007 17:14:27 +0100 Message-ID: <1180973667.4041.18.camel@localhost.localdomain> References: <20070530214638.GA21589@fc.hp.com> <1180598644.29571.57.camel@localhost.localdomain> <1180627325.16734.26.camel@basalt> <1180628637.29571.84.camel@localhost.localdomain> <1180967986.6221.133.camel@bling> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1180967986.6221.133.camel@bling> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Alex Williamson Cc: Aron Griffis , xen-devel@lists.xensource.com, Hollis Blanchard List-Id: xen-devel@lists.xenproject.org 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.