Pkg xen devel - Dec 2011 - Moving XenAPI python modules in a separate binary

Hi Mike and Jon,

If I do this:
dpkg -S /usr/lib/python2.7/dist-packages/XenAPI.py

then I can see that the XenAPI python package is in fact xcp-xapi. This
is quite annoying, because I will need it when building OpenStack nova,
but xcp-xapi depends on the Xen hypervisor, which I don't care about
when building Openstack. Said in another way: I'd like to avoid having
to put "xcp-xapi" as Build-Depends: for nova.

So I was wondering, would it be possible to have all python stuff
packaged in a separate binary, like python-xen-api or something like
that like python-xapi, python-xcp? (which one has your preference?)

Thomas

On 12/28/11, Thomas Goirand <thomas at goirand.fr>
wrote:
> Hi Mike and Jon,
>
> If I do this:
> dpkg -S /usr/lib/python2.7/dist-packages/XenAPI.py
>
> then I can see that the XenAPI python package is in fact xcp-xapi. This
> is quite annoying, because I will need it when building OpenStack nova,
> but xcp-xapi depends on the Xen hypervisor, which I don't care about
> when building Openstack. Said in another way: I'd like to avoid having
> to put "xcp-xapi" as Build-Depends: for nova.
>
> So I was wondering, would it be possible to have all python stuff
> packaged in a separate binary, like python-xen-api or something like
> that like python-xapi, python-xcp? (which one has your preference?)
>
I like the sound of 'python-xenapi', since that's what the module is
called. 'python-xapi' would also be acceptable to me. Any other
opinions?

Mike