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/
Home Products Support Community News


Re: [Xen-devel] new repo layout?

To: Aron Griffis <aron@xxxxxx>
Subject: Re: [Xen-devel] new repo layout?
From: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>
Date: Thu, 31 May 2007 09:04:04 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 31 May 2007 01:02:21 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20070530214638.GA21589@xxxxxxxxx>
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>
References: <20070530214638.GA21589@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Wed, 2007-05-30 at 17:46 -0400, Aron Griffis wrote:
> Could somebody at XenSource comment on the details of the planned repo
> changes, i.e. how things will work in the non-sparse world?  For
> example, what header files will live in the HV vs. the kernel? 
> Will the HV, tools, kernel typically be built simultaneously as they
> are now, or will they be built separately?

>From the point of view of someone who has cloned xen-unstable.hg and run
"make world/dist/etc" there should be no difference in what gets built.
The current tarball download+unpack+patch+sparse phases will simply be
replaced by an hg clone phase. There are already options to build other
trees as well, i.e. "make linux-2.6-paravirt-build" will build the
latest release of the paravirt_ops tree with Xen support from 

Each OS tree is expected to carry its own set of self-contained headers
consistent with its needs -- this has always been the case for all trees
apart from the sparse tree. For the tree which is going to be derived
from the sparse tree the build will check that the hypervisor headers
(xen/include/public) and the kernel headers
(linux-FOO.hg/include/xen/interface/) are in sync and error out in order
to prevent those two trees diverging.


Xen-devel mailing list

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