From: "Daniel P. Berrangé" <berrange@redhat.com>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: Joelle van Dyne <j@getutm.app>, qemu-devel@nongnu.org
Subject: Re: [PATCH 04/10] meson: option to build as shared library
Date: Tue, 13 Oct 2020 15:46:25 +0100 [thread overview]
Message-ID: <20201013144625.GP70612@redhat.com> (raw)
In-Reply-To: <e27acf2-4dbe-4674-78cc-67aa7b505c54@eik.bme.hu>
On Tue, Oct 13, 2020 at 04:41:06PM +0200, BALATON Zoltan wrote:
> On Tue, 13 Oct 2020, Daniel P. Berrangé wrote:
> > On Mon, Oct 12, 2020 at 04:29:33PM -0700, Joelle van Dyne wrote:
> > > From: osy <osy86@users.noreply.github.com>
> > >
> > > On iOS, we cannot fork() new processes, so the best way to load QEMU into an
> > > app is through a shared library. We add a new configure option
> > > `--enable-shared-lib` that will build the bulk of QEMU into a shared lib.
> > > The usual executables will then link to the library.
> >
> > Note that QEMU as a combined work is licensed GPLv2-only, so if an app is
> > linking to it as a shared library, the application's license has to be
> > GPLv2 compatible. I fear that shipping as a shared library is an easy way
> > for apps to get into a license violating situation without realizing.
>
> Please don't let that be an obstacle in merging this series. They'll do it
> anyway as seen here so having it upstream is probably better than having a
> lot of different/divergent forks.
"They'll violate the license anyway" is not a compelling argument.
> In case of UTM it seems to be licensed under Apache License 2.0:
>
> https://github.com/utmapp/UTM/blob/master/LICENSE
>
> which FSF says not compatible with GPLv2 but it is with GPLv3:
>
> http://www.gnu.org/licenses/license-list.html#apache2
>
> Not sure however if that's for using Apache licenced part in GPLv2 code or
> the other way around like in UTM in which case I think the whole work will
> effectively become GPLv3 as most parts of QEMU is probably GPLv2+ already or
> BSD like free that should be possible to combine with only files explicitely
> GPLv2 in QEMU remaining at that license and UTM parts are Apache 2.0 when
> separated from QEMU. I have no idea about legal stuff whatsoever but
> combining two free software components should be legal some way (otherwise
> it's not possible to combine GPLv2 with GPLv3 either).
You need to distinguish between GPLv2-only and GPLv2-or-later.
GPLv2-or-later is fine as that upgrades to GPLv3 when used in a
combined work with Apache License or GPLv3 software.
GPLv2-only will, by design, *not* upgrade to newer GPL versions
when combined - it is simply license incompatible.
QEMU unfortunately has a bunch a GPLv2-only code present that we
cannot eliminate.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2020-10-13 14:48 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 23:29 [PATCH 00/10] iOS and Apple Silicon host support Joelle van Dyne
2020-10-12 23:29 ` [PATCH 01/10] configure: option to disable host block devices Joelle van Dyne
2020-10-12 23:29 ` [PATCH 02/10] configure: cross-compiling without cross_prefix Joelle van Dyne
2020-10-12 23:29 ` [PATCH 03/10] qemu: add support for iOS host Joelle van Dyne
2020-10-12 23:29 ` [PATCH 04/10] meson: option to build as shared library Joelle van Dyne
2020-10-13 7:51 ` Daniel P. Berrangé
2020-10-13 14:41 ` BALATON Zoltan via
2020-10-13 14:46 ` Daniel P. Berrangé [this message]
2020-10-13 15:16 ` Joelle van Dyne
2020-10-13 15:57 ` Daniel P. Berrangé
2020-10-13 16:40 ` BALATON Zoltan via
2020-10-14 16:09 ` Joelle van Dyne
2020-10-13 15:23 ` BALATON Zoltan via
2020-10-12 23:29 ` [PATCH 05/10] slirp: update for iOS resolv fix Joelle van Dyne
2020-10-13 13:32 ` Philippe Mathieu-Daudé
2020-10-13 14:38 ` Marc-André Lureau
2020-10-13 14:59 ` Philippe Mathieu-Daudé
2020-10-14 15:54 ` Joelle van Dyne
2020-10-12 23:29 ` [PATCH 06/10] coroutine: add libucontext as external library Joelle van Dyne
2020-10-13 13:31 ` Stefan Hajnoczi
2020-10-13 14:49 ` BALATON Zoltan via
2020-10-13 15:25 ` Joelle van Dyne
2020-10-13 16:18 ` Daniel P. Berrangé
2020-10-12 23:29 ` [PATCH 07/10] tcg: implement bulletproof JIT Joelle van Dyne
2020-10-13 8:22 ` Philippe Mathieu-Daudé
2020-10-13 14:58 ` BALATON Zoltan via
2020-10-14 16:03 ` Joelle van Dyne
2020-10-14 20:35 ` Richard Henderson
2020-10-14 20:54 ` BALATON Zoltan via
2020-10-14 21:40 ` Richard Henderson
2020-10-14 20:58 ` Joelle van Dyne
2020-10-14 21:08 ` BALATON Zoltan via
2020-10-14 21:49 ` Richard Henderson
2020-10-14 22:54 ` Joelle van Dyne
2020-10-12 23:29 ` [PATCH 08/10] tcg: mirror mapping RWX pages for iOS optional Joelle van Dyne
2020-10-13 13:52 ` Paolo Bonzini
2020-10-13 15:10 ` Joelle van Dyne
2020-10-12 23:29 ` [PATCH 09/10] tcg: support JIT on Apple Silicon Joelle van Dyne
2020-10-13 13:55 ` Paolo Bonzini
2020-10-13 14:09 ` Peter Maydell
2020-10-13 15:13 ` Joelle van Dyne
2020-10-12 23:29 ` [PATCH 10/10] block: check availablity for preadv/pwritev on mac Joelle van Dyne
2020-10-13 1:21 ` [PATCH 00/10] iOS and Apple Silicon host support no-reply
2020-10-13 2:12 ` Joelle van Dyne
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=20201013144625.GP70612@redhat.com \
--to=berrange@redhat.com \
--cc=balaton@eik.bme.hu \
--cc=j@getutm.app \
--cc=qemu-devel@nongnu.org \
/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).