From: Vincent Hanquez <vincent.hanquez@eu.citrix.com>
To: Jun Koi <junkoi2004@gmail.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: [ANNOUNCE] libxenlight
Date: Mon, 09 Nov 2009 14:59:46 +0000 [thread overview]
Message-ID: <4AF82E62.904@eu.citrix.com> (raw)
In-Reply-To: <fdaac4d50911090645k205e3bbi3d068fc217b515fc@mail.gmail.com>
Jun Koi wrote:
> Hi Stefano,
>
> Is this yet-another-GPL lib? If so, that is really disappointed.
>
>
> I think people desperately need LGPL code like this, but not GPL. So
> please make it LGPL for people to use.
>
> Personally, I have some small projects, and I had to reimplement a
> part of libxc under LGPL. If libxenlight is under LGPL, I dont have to
> waste my time doing that.
>
> I believe that libvirt doesnt want this code, because of
>
> incompatibility issue: libvirt is LGPL, which is more free, IMO.
>
Hi Jun,
The library by itself is released under the LGPLv2 license. However,
since it's linked to the xenguest and xencontrol libraries which are
both GPLv2, you cannot use it in a LGPL context yet, but only in a GPL
context (unless you can replace all xenguest/xc calls to some libraries
of your own).
we do have another implementation of libxc that is LGPL (rewritten from
scratch) that is available in the xencloud api-libs tree. however a
reimplemented version (or relicensed version) of xenguest is still
missing for now.
--
Vincent
next prev parent reply other threads:[~2009-11-09 14:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-09 14:04 [ANNOUNCE] libxenlight Stefano Stabellini
2009-11-09 14:45 ` Jun Koi
2009-11-09 14:59 ` Vincent Hanquez [this message]
2009-11-09 17:41 ` Ian Jackson
2009-11-10 12:44 ` Tim Post
2009-11-19 18:51 ` Pasi Kärkkäinen
2009-11-19 19:43 ` Stefano Stabellini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AF82E62.904@eu.citrix.com \
--to=vincent.hanquez@eu.citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=junkoi2004@gmail.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.