On Tue, May 26, 2009 at 04:26:36PM +0200, Ruben S. Montero wrote: > Hi, > > Probably the easiest way to solve this is to get rid to of the > OpenNebula client library. So we do not have the license issue and, as > Daniel said, we do not have to include the C++ dependencies. > > We'll try to send the patch ASAP. Okay, thanks ! Ideally by Friday since I will release 0.6.4 then, if we could have this fixed before the realease that would be great :-) Daniel > On Tue, May 26, 2009 at 3:16 PM, Daniel P. Berrange <berrange@xxxxxxxxxx> wrote: [...] > >> 6. talk XML RPC directly to the server and not use the client APIs > > > > After looking at the scope of the APIs, I'm inclined to say we should > > take option 6. The current impl > > > > - libvirt one driver -> one C client > > - one C client is a wrapper around one C++ client > > - one C++ client talks to XMLRPC-C C++ library > > - XMLRPC-C C++ library is a wrapper around XMLRPC-C library > > > > So, not only do we currently have a license problem, but we're pulling in the > > whole C++ runtime for no particularly good reason or benefit. The APIs being > > invoked from the libvirt ONE driver are pretty simple - even the C++ client > > library is a merely couple of 100 lines of code. So I think its pretty easy > > to just have the libvirt one driver use xmlrpc C library directly. > > > > Regards, > > Daniel -- Daniel Veillard | libxml Gnome XML XSLT toolkit http://xmlsoft.org/ daniel@xxxxxxxxxxxx | Rpmfind RPM search engine http://rpmfind.net/ http://veillard.com/ | virtualization library http://libvirt.org/ -- Libvir-list mailing list Libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list