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] HVM support to be removed from Debian Squeeze: call for

To: Thomas Goirand <thomas@xxxxxxxxxx>
Subject: Re: [Xen-devel] HVM support to be removed from Debian Squeeze: call for volunteers
From: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Date: Wed, 16 Dec 2009 11:18:50 +0000
Cc: Bastian Blank <waldi@xxxxxxxxxx>, Debian Xen Team <pkg-xen-devel@xxxxxxxxxxxxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 16 Dec 2009 03:19:24 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4B27C3FA.7060805@xxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4B2717A1.2030503@xxxxxxxxxx> <19239.43841.305068.90197@xxxxxxxxxxxxxxxxxxxxxxxx> <4B27C3FA.7060805@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thomas Goirand writes ("Re: [Xen-devel] HVM support to be removed from Debian 
Squeeze: call for volunteers"):
> To me, that's the most easy way, yes, because this avoids the
> double-work of listing files to install (once in the "make install" and
> once in the debian/install).

Quite so.

> Yes, because Debian uses versionned folders for /usr/lib/xen. Maybe we
> could overwrite this in the Makefile with a variable. That's what I did
> for numerous projects so that "make install" could be used by a spec
> file using "make install MANUAL_DIR=%{_mandir}" for example. What do you
> think? Could this apply to this project?

I've been thinking about this and I'm not sure the versioned folders
still make sense.  But if you want to send sensible patches to the Xen
build system to allow the interposing of a version number, I guess we
would accept them (after review).

> > But partitioning the output of `make dist-tools' etc. to provide
> > something that can be used for qemu-dm build should be easy enough.
> What do you mean here here? What's the use of "make dist-tools"?

It's one of the targets in the upstream top-level Makefile.  The Xen
top-level Makefile doesn't use the conventional target names.
"dist-foo" means install "foo" in dist/install/.

> One of my issue is to create the .orig.tar.gz with only the relevant
> code, I'm not sure where to start. Could you do that? Maybe add a target
> to the "upstream" Makefile? How should we do it?

To build qemu-dm you need two things: the actual source code to
qemu-dm which is in a separate repository.  When we make the official
Xen tarballs we don't provide a separate tarball; we include it in the
same tree.  But the xen-unstable tree downloads the qemu-dm source
from the git repository.

So I would suggest you invent an orig.tar.gz by using git-archive
after fetching a suitably tagged qemu tree from

The other thing you need is the development headers and libraries
whose source code is in the Xen hg tree.  The qemu-dm source code
isn't set up for building from an "installed" copy of those libraries.
For example it includes, at build-time, fragments of makefiles from
the Xen build tree.

It would probably be possible to make a build work given a version of
these libraries and headers.  I can help with this but first we need a
libxen-dev package that contains libxc, libxs, libxenguest, etc.

> Can you start a project on Alioth, with a git repo? Would it be useful
> (I never used alioth or gforge yet)?

I'm happy to do that.  I'll try to get that set up.  I find Alioth's
git support confusing at times so it may not happen right away.


Xen-devel mailing list

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