From: Stefano Babic <sbabic@denx.de>
To: Neal Gompa <ngompa13@gmail.com>, Stefano Babic <sbabic@denx.de>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>,
Omar Sandoval <osandov@osandov.com>,
David Sterba <dsterba@suse.com>
Subject: Re: btrfs-progs license
Date: Tue, 8 Dec 2020 14:25:16 +0100 [thread overview]
Message-ID: <4e94f309-2fed-7ad6-a322-1dcfeaeb5c6d@denx.de> (raw)
In-Reply-To: <CAEg-Je9iUAn+9H7p+qm8D+bSY382VkTKZ0H4ExNLePAEZT9nEA@mail.gmail.com>
Hi Neal,
On 08.12.20 13:37, Neal Gompa wrote:
> On Tue, Dec 8, 2020 at 4:52 AM Stefano Babic <sbabic@denx.de> 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.
>>
>
> Please don't use this phrasing, because it's not true. There is no
> circumstance where the GNU version 3 licenses (GPL, LGPL, AGPL) are
> incompatible with secure boot environments. What you're talking about
> is an additional restriction *you* are imposing in which you don't
> want to make it possible for the software to be user-serviceable for
> any purpose. That's not the same thing as "secure boot".
>
Sorry for misunderstanding, you're right - but you have perfectly
understood what I meant ;-)
>> 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 ?
>>
>
> I'm not sure there is a conflict, but there are relatively few authors
> of the libbtrfsutil code, so we could get the license downgraded to
> LGPLv2+ instead of being LGPLv3+.
This would be really nice !
Regards,
Stefano
--
=====================================================================
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 prev parent reply other threads:[~2020-12-08 13:26 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 [this message]
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=4e94f309-2fed-7ad6-a322-1dcfeaeb5c6d@denx.de \
--to=sbabic@denx.de \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=ngompa13@gmail.com \
--cc=osandov@osandov.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