qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Saggi Mizrahi <smizrahi@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] Added target to build libvdisk
Date: Tue, 23 Aug 2011 17:12:39 +0100	[thread overview]
Message-ID: <20110823161239.GO5728@redhat.com> (raw)
In-Reply-To: <4E52ADFC.5070506@redhat.com>

On Mon, Aug 22, 2011 at 02:29:00PM -0500, Anthony Liguori wrote:
> On 08/22/2011 12:06 PM, Saggi Mizrahi wrote:
> >libvdisk is a library that packages qemu's handling of disk images. This
> >allows for other programs to link to it and get access to qemu image
> >file abstractions.
> >
> >To use install the lib and #include<vdisk/block.h>
> >all the bdrv_* functions work as expected.
> >
> >Signed-off-by: Saggi Mizrahi<smizrahi@redhat.com>
> 
> It's a good idea in principle but the approach is far too naive.
> 
> The block layer needs a good bit of modularization first.  Test
> cases need to be written, and most importantly, using the library
> shouldn't require writing a bunch of dummy functions.

There are also licensing practicalities which can cause us
some trouble/pain. For example:

> >  ######################################################################
> >+# libvdisk
> >+
> >+vdisk-obj-y = $(block-obj-y)
> >+
> >+vdisk-obj-y += qemu-tool.o qemu-error.o
> >+vdisk-obj-y += $(oslib-obj-y) $(trace-obj-y) $(block-obj-y)
> >+vdisk-obj-y += $(qobject-obj-y) $(version-obj-y) qemu-timer-common.o

$(block-obj-y) pulls in  'aio.o' which is built from aio.c which
is licensed  "GPLv2 only". So even those many files are BSD
licenses, the combined work will be GPLv2-only. Unfortunately ending
up with a libqemublock.so which is GPLv2-only is as good as useless
for libs/apps since it is incompatible with both LGPLv2(+) and GPLv3.

Now in this case aio.c is labelled as Copyright IBM / Anthony,
so IBM could likely resolve this licensing to be more widely
compatible. This could^H^Hwould become a non-trivial task if we
need to look at many files & then also any patches accepted to
those files from 3rd parties over the years :-(

Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|

  reply	other threads:[~2011-08-23 16:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-22 17:06 [Qemu-devel] [PATCH 1/2] Better support for distros using lib64 dis Saggi Mizrahi
2011-08-22 17:06 ` [Qemu-devel] [PATCH 2/2] Added target to build libvdisk Saggi Mizrahi
2011-08-22 18:50   ` Blue Swirl
2011-08-22 19:29   ` Anthony Liguori
2011-08-23 16:12     ` Daniel P. Berrange [this message]
2011-08-23 16:14       ` Anthony Liguori
2011-08-23 16:18         ` Daniel P. Berrange
2011-08-23 16:21           ` Anthony Liguori
2011-08-24 11:32             ` Saggi Mizrahi
2011-08-24 12:50               ` Anthony Liguori
2011-08-24 12:55                 ` Daniel P. Berrange

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=20110823161239.GO5728@redhat.com \
    --to=berrange@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=qemu-devel@nongnu.org \
    --cc=smizrahi@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).