Ian Campbell
2012-Oct-04 08:54 UTC
[Pkg-xen-devel] My Xen package plans/thoughts/ideas for Jessie
Waldi, There's a few things I'm intending to look at for the Xen packaging in Jessie, which I thought it might be useful to share with you. If there's anything on this list you explicitly do not want done please let me know so I don't waste my time, likewise if there are any which you intend to work on yourself. Otherwise I shall tackle these as and when I get a chance and post patches. Unordered list: * UEFI support. Build and install the necessary hypervisor binary. Integrate with bootloaders as necessary. * Enable ARM port. Depends on upstream progress of course, but once this is in reasonable shape I'd obviously want to enable it for armhf and arm64. * Toolstack virtual package, split existing package into common, xm/xend and xl. xcp-xapi could also provide the virtual package allowing only the desired toolstack to be installed. * Rejig the tools install targets to allow use of dh_install --list-missing or --fail-missing. I'm not sure if this is worthwhile but there's a small number of bugs filed about missing this and that (e.g. man pages) which might have been avoided if we could use these. This might be a case of trying it and seeing. * There's a handful of normal and minor priority bugs which look pretty easy/quick to fix. Not really a packaging thing but I also wonder how hard it would be to set up a CIA^WKGB (or similar) bot for pkg-xen. Ian. -- Ian Campbell Current Noise: Paradise Lost - In This We Dwell Your aim is high and to the right.
Bastian Blank
2012-Oct-04 13:43 UTC
[Pkg-xen-devel] My Xen package plans/thoughts/ideas for Jessie
On Thu, Oct 04, 2012 at 09:54:40AM +0100, Ian Campbell wrote:> * UEFI support. Build and install the necessary hypervisor binary. > Integrate with bootloaders as necessary.Can't it use the same binary for UEFI and BIOS like Linux does since a long time?> * Enable ARM port. Depends on upstream progress of course, but > once this is in reasonable shape I'd obviously want to enable it > for armhf and arm64.No problem.> * Toolstack virtual package, split existing package into common, > xm/xend and xl. xcp-xapi could also provide the virtual package > allowing only the desired toolstack to be installed.Please describe this a bit more.> * Rejig the tools install targets to allow use of dh_install > --list-missing or --fail-missing. I'm not sure if this is > worthwhile but there's a small number of bugs filed about > missing this and that (e.g. man pages) which might have been > avoided if we could use these. This might be a case of trying it > and seeing.Not sure what you think about. But please notice that the xen package build both arch-all and other packages, so you can't move it into one target. Bastian -- Ahead warp factor one, Mr. Sulu.
Apparently Analagous Threads
- [PATCH 6/7] Create 2 ocaml packages, libxen-4.1-ocaml and libxen-4.1-ocaml-dev.
- Bug#711273: xen-hypervisor-4.2-amd64: Acn't re-create domains after migration from 4.1 to 4.2
- the EXTRAVERSION problem in dh-kpatches...
- [OCAML 0/7] V4 or so of the xen ocaml packaging patches
- Driver domains communication protocol proposal