[Pkg-xen-devel] [patch] Packages ocaml libraries

Ian Campbell ijc at hellion.org.uk
Mon Oct 3 18:56:33 UTC 2011


On Tue, 2011-10-04 at 01:31 +0800, Thomas Goirand wrote:
> On 10/03/2011 06:13 PM, Ian Campbell wrote:
> > On Sun, 2011-10-02 at 14:49 +0800, Thomas Goirand wrote:
> >> On 09/09/2011 12:13 PM, Thomas Goirand wrote:
> >>> Mike, Jonathan, can we have your useful comment on this? Namely:
> >>> - Is your uuidm a fork of libuuidm-ocaml-dev? Can you make it so we use
> >>> that one instead of what's in Xen 4.1.1?
> >>> - Can we use @OCamlStdlibDir@/xen/libname for all the files that aren't
> >>> .so? Will it be an issue later?
> >>>
> >>> We really need your feedback here. Also, I tried once more to build
> >>> xen-api-libs in SID, and it failed to build, even with the
> >>> xen-api-libs-debian patches from Jonathan. Can you look into that so we
> >>> can move forward with this packaging as well?
> >>>
> >>> Thomas
> >>
> >> Hi,
> >>
> >> I had a reply from Jon about 10 days ago, where he tells he is ok with
> >> using a "xen" folder for the ocaml libs, but had no time to rewrite the
> >> patch corresponding to it. Here it is, attached to this message, moving
> >> all non-.so files into @OCamlStdlibDir@/xen/${folder}.
> > 
> > Jon recently (the end of last week) posted a patch series to xen-devel
> > to implement the renaming he mentions below ("xc->xenctrl, xs->xenstore,
> > xb->xenbus, xl->xenlight").
> >
> > Since this is likely to be the change we
> > make upstream we may as well make the packaging conform to that scheme
> > now too. I think the xen prefix is as good as using the xen subfolder.
> > 
> > He also posted a patch to remove the uuid and log libraries so we may as
> > well not package those (presumably he has a patch to make xapi not
> > require them).
> > 
> > That just leaves the mmap library. It's unclear what it's future is but
> > I suppose we may as well package it as xenmmap for consistency with the
> > others?
> > 
> > Ian.
> 
> So, in a shorter way, are you asking me to *not* do the packaging work,
> and wait for the next upstream version of Xen?

No. I'm saying that whatever packaging gets done may as well match what
the next upstream release is going to use, or you will just need to have
another transition.

> I've spent a quite big amount of time, involved the Ocaml Task Force,
> tried building xen-api-libs, etc., in the hope of having Xen-Api in the
> long run, but all this is now bring to a halt, just because of the
> decision to change the folder names, which doesn't match my current work
> (did it mater so much?). All this seems pretty counter-productive to me. :/

The names Jon proposed upstream are the same ones which he proposed as
the long term solution in his initial mail which you quoted in
<4E88096F.1010906 at debian.org>. I'm not sure why we would want a
different naming scheme in the short term.

> 
> When is the next release of Xen?

Not set in stone yet but I would expect towards the end of this year,
beginning of next.

Ian.

> 
> Thomas
> 

-- 
Ian Campbell


Will the third world war keep "Bosom Buddies" off the air?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20111003/186dd8e4/attachment.pgp>


More information about the Pkg-xen-devel mailing list