From: Omar Sandoval <osandov@osandov.com>
To: Stefano Babic <sbabic@denx.de>
Cc: linux-btrfs@vger.kernel.org, David Sterba <dsterba@suse.com>
Subject: Re: btrfs-progs license
Date: Tue, 8 Dec 2020 13:00:01 -0800 [thread overview]
Message-ID: <X8/pUT3B1+uluATv@relinquished.localdomain> (raw)
In-Reply-To: <b927ca28-e280-4d79-184f-b72867dbdaa8@denx.de>
On Tue, Dec 08, 2020 at 10:49:10AM +0100, Stefano Babic wrote:
> 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.
libbtrfsutil is LGPLv3, where did you get the idea that it is GPLv3?
> 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 ?
No objections from me to make it LGPLv2 instead, I suppose. Dave,
thoughts?
next prev parent reply other threads:[~2020-12-08 21:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 9:49 btrfs-progs license Stefano Babic
2020-12-08 10:32 ` 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 [this message]
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=X8/pUT3B1+uluATv@relinquished.localdomain \
--to=osandov@osandov.com \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=sbabic@denx.de \
/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.