linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefano Babic <sbabic@denx.de>
To: ronnie sahlberg <ronniesahlberg@gmail.com>,
	Stefano Babic <sbabic@denx.de>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs-progs license
Date: Tue, 8 Dec 2020 11:41:40 +0100	[thread overview]
Message-ID: <fe343645-4919-a09c-2205-5d84ed9a9ecd@denx.de> (raw)
In-Reply-To: <CAN05THRxZq87K3YiHzDjHR+n4uPEWx1ocNWrWXBGr3Pi-sZF2g@mail.gmail.com>

Hi Ronnie,

On 08.12.20 11:32, ronnie sahlberg wrote:
> On Tue, Dec 8, 2020 at 7:53 PM 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.
>>
>> 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 ?
>>
> 
> There are always paths when licences conflict.
> One path I have used successfully in other projectss is just to write
> a replacement from scratch
> picking a licence I am more comfortable with.
> 

Yes, I come to the same conclusion - but before doing this, I just check
if there is an option to reuse existing code. Anyway, btrfs-progs
license already conflicts due to libbtrfutil and it should be set to
GPLv3, and in my understanding even the utility "btrfs" should be
avoided on many embedded systems if GPLv3 is not allowed (it is still
marked as GPLv2 in Openembedded). Am I right (no lawyer here !) ?

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
=====================================================================

  reply	other threads:[~2020-12-08 10:42 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 [this message]
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=fe343645-4919-a09c-2205-5d84ed9a9ecd@denx.de \
    --to=sbabic@denx.de \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=ronniesahlberg@gmail.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;
as well as URLs for NNTP newsgroup(s).