[libvirt] [PATCH 1/1] [RFC] Parallels Server Bare Metal driver stub
Daniel Veillard
veillard at redhat.com
Wed Sep 28 14:08:37 UTC 2011
On Wed, Sep 28, 2011 at 06:01:24PM +0400, Dmitry Mishin wrote:
>
> On Wednesday, September 28, 2011 05:34:47 PM Daniel Veillard wrote:
> [...]
> > > +int psbmApiInit(struct psbm_driver *driver)
> > > +{
> > > + const char *libname = "libprl_sdk.so";
> > > + void *handle = NULL;
> > > + PRL_RESULT res;
> >
> > That I dislike, sorry this must not be dlopen'ed in at runtime,
> > but checked in at configure time and properly linked in. Also
> > means that proper dependancies and packaging have to be in place.
> I exactly want to avoid dependencies.
>
> Library can be used both remotely (for example, on Fedora host) and locally
> (on PSBM host). And if in the local case we can create special libvirt rpm
> with enabled PSBM support and integrate it to distribution, in remote case we
> force user to download not only Parallels SDK rpm (which will hardly be
> included to Fedora due to proprietary license), but also fixed libvirt package
> instead of already installed one. Is it preferable way from your point of
> view?
That sounds fairly evil, I guess I would make a fuss if you started
shipping libvirt rpms with non libvirt code in it. I think you need to
go the XML-RPC way since that how access to the server seems to work,
see my second mail, Matthias did this for VMWare support...
> >
> > > + handle = dlopen(libname, RTLD_LAZY);
> > > + if (!handle) {
> > > + psbmError(VIR_ERR_INTERNAL_ERROR,
> > > + _("Failed to load SDK library %s %s"), libname,
> > > dlerror()); + return VIR_ERR_INTERNAL_ERROR;
> > > + }
> >
> > So what is that SDK library, how is it distributed and what is the
> > licencing for it ? As much as I like adding a driver, I would like to
> > make sure the deployement is clean and there is no licencing issues.
> >
> > Any pointers ? All I found was
> > http://www.parallels.com/ptn/download/sdk/
> > and it's quite silent on code availability and Licence for the
> > libraries.
> It has a proprietary license and not open sourced now. Is it a problem?
Yes our code is LGPL or GPL, we can't link with your SDK if it's
not released under a compatible licence. See my second mail,
Daniel
--
Daniel Veillard | libxml Gnome XML XSLT toolkit http://xmlsoft.org/
daniel at veillard.com | Rpmfind RPM search engine http://rpmfind.net/
http://veillard.com/ | virtualization library http://libvirt.org/
More information about the libvir-list
mailing list