[systemd-devel] Systemd license vs. libcryptsetup license
k.jackiewicz at samsung.com
Wed Jun 7 07:49:44 UTC 2017
I guess the "conflict" was not the best word to describe it.
If I want to release a product with systemd the libryptsetup option will
force me to release it under GPL. Is that correct?
From: Zbigniew Jędrzejewski-Szmek [mailto:zbyszek at in.waw.pl]
Sent: Tuesday, June 06, 2017 5:00 PM
To: Krzysztof Jackiewicz
Cc: systemd-devel at lists.freedesktop.org
Subject: Re: [systemd-devel] Systemd license vs. libcryptsetup license
On Tue, Jun 06, 2017 at 04:33:11PM +0200, Krzysztof Jackiewicz wrote:
> I noticed that when systemd is configured with libcryptsetup option
> enabled it will link to libcryptsetup which is distributed under GPL
> 2.0. It seems like a license conflict to me. Can anyone explain it?
A license conflict appears when two pieces of software are combined and the
licenses have incompatible terms, so they cannot be both satisfied at the
same time. Systemd is LGPL which is compatible with GPL and pretty much
anything else. Also, we don't distribute the combined product, which is the
only thing LGPL and GPL put any conditions on.
More information about the systemd-devel