From: Stefano Babic <sbabic@denx.de>
To: linux-btrfs@vger.kernel.org
Cc: stefano babic <sbabic@denx.de>
Subject: btrfs-progs license
Date: Tue, 8 Dec 2020 10:49:10 +0100 [thread overview]
Message-ID: <b927ca28-e280-4d79-184f-b72867dbdaa8@denx.de> (raw)
Hi,
I hope I am not OT. I ask about license for btrfs-progs and related
libraries. I would like to use libbtrfsutils in a FOSS project, but this
is licensed under GPLv3 (even not LGPL) and it forbids to use it in
projects where secure boot is used.
Checking code in btrfs-progs, btrfs is licensed under GPv2 (fine !) and
also libbtrfs. But I read also that libbtrfs is thought to be dropped
from the project. And checking btrfs, this is linked against
libbtrfsutils, making the whole project GPLv3 (and again, not suitable
for many industrial applications in embedded systems).
Does anybody explain me the conflict in license and if there is a path
for a GPLv2 compliant library ?
Best regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic@denx.de
=====================================================================
next reply other threads:[~2020-12-08 9:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 9:49 Stefano Babic [this message]
2020-12-08 10:32 ` btrfs-progs license ronnie sahlberg
2020-12-08 10:41 ` Stefano Babic
2020-12-08 12:37 ` Neal Gompa
2020-12-08 13:25 ` Stefano Babic
2020-12-08 21:00 ` Omar Sandoval
2020-12-10 11:27 ` David Sterba
2020-12-10 12:03 ` Stefano Babic
2021-01-14 18:47 ` David Sterba
2021-01-14 20:00 ` Stefano Babic
2021-01-14 19:38 ` Neal Gompa
2021-01-14 20:16 ` Stefano Babic
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=b927ca28-e280-4d79-184f-b72867dbdaa8@denx.de \
--to=sbabic@denx.de \
--cc=linux-btrfs@vger.kernel.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).