[Pkg-xen-devel] My Xen package plans/thoughts/ideas for Jessie

[Bastian Blank]

On Fri, Oct 05, 2012 at 11:49:48AM +0100, Ian Campbell wrote:
> This allows people to only install the toolstack they are interested in
> using, helps us transition from xend->xl and to deprecate xend when the
> time comes. I suspect it could also be used to simplify the $TOOLSTACK
> stuff via /etc/defaults/xen.

What are the advantages for the users and the maintainers?

> It's an open question whether the xen-toolstack-*-X.Y packages should
> also conflict/replace xen-toolstack-X.Y. It seems like being able to
> install e.g. xl and xcp-xapi simultaneously might be somewhat useful for
> debugging and things like that.

Does this work?

> There's probably scope for going even more fine grained splitting e.g.
> put the language bindings in their own packages and splitting up the
> various classes of utils a bit but I think that would be taking things
> too far.

Adding new packages highers the costs for all users. So adding packages
just for fun is not the way to go.

>       * Enable ocaml xenstored (oxenstored). Not sure if we do this
>         already done in the 4.2 packaging. I'd like to make it the
>         default if possible. Not sure if this is worth dual packages
>         allowing users to choose or if we should just pick one.

Unlikely, unless it just does it without me noticing it.

>       * Package libxenlight so others can link against it, at least
>         libvirt and xcp-xapi (at some point in the future) are going to
>         want to do this.

With the lib in the current state? Not until the error checking stuff is
actually worked out. Memory management routing must never call exit if
they can't make sure it does not break stuff.

Bastian

-- 
Bones: "The man's DEAD, Jim!"