On Tue, Nov 12, 2013 at 9:09 PM, Daniel Veillard
<veillard(a)redhat.com> wrote:
> On Tue, Nov 12, 2013 at 06:21:43PM +0000, Daniel P. Berrange wrote:
>> From: "Daniel P. Berrange" <berrange(a)redhat.com>
>>
>> This patch series is a followup to
>>
>>
https://www.redhat.com/archives/libvir-list/2013-September/msg00413.html
>>
>> to split the python binding out into a separate GIT repository.
>>
>> These patches do not apply to current GIT. Instead you have to first
>> create a new git repo, initializing based on the history of the
>> python/ subdirectory.
>
> I didn't really had time to do the steps below, but a general ACK
> on the direction, it will be hard to really test without having the
> 2 directories and I'm sure something will bite me at the next release
> time, isn't it ;-) ?
> For the python3 patches that I had tried to isolate based on libxml2
> port I made last year I think it wont be much harder to do on the new
> separate git than currently so that should not get in the way,
>
> IMHO go for it,
>
> Daniel
I was actually asked by some OpenStack guys to help separate this out
so I'm working from Dan's patches to try to add the pieces we want
before releasing from this route.
Yep, the main piece that would be a blocker for OpenStack to use this
is the ability to have the python version == x.y.z be able to build against
any libvirt <= x.y.z, instead of libvirt == x.y.z
Daniel
--
|: