All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] btrfs-progs: bump to version 4.16
Date: Wed, 11 Apr 2018 09:10:04 +0200	[thread overview]
Message-ID: <20180411091004.6486eda3@windsurf> (raw)
In-Reply-To: <c92f59e6efd59c9f887a81c2007d7d2962d45064.1523421916.git.baruch@tkos.co.il>

Hello,

On Wed, 11 Apr 2018 07:45:16 +0300, Baruch Siach wrote:
> Drop upstream patch.
> 
> Add a patch for fixing static build.
> 
> Add license information about the newly introduced libbtrfsutil.
> 
> Disable the libbtrfsutil python binding. It does not cross compile
> nicely.
> 
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>

Thanks for this update. One question below.

> -BTRFS_PROGS_VERSION = 4.15.1
> +BTRFS_PROGS_VERSION = 4.16
>  BTRFS_PROGS_SITE = $(BR2_KERNEL_MIRROR)/linux/kernel/people/kdave/btrfs-progs
>  BTRFS_PROGS_SOURCE = btrfs-progs-v$(BTRFS_PROGS_VERSION).tar.xz
>  BTRFS_PROGS_DEPENDENCIES = host-pkgconf e2fsprogs lzo util-linux zlib
> -BTRFS_PROGS_CONF_OPTS = --disable-backtrace --disable-zstd
> -BTRFS_PROGS_LICENSE = GPL-2.0
> -BTRFS_PROGS_LICENSE_FILES = COPYING
> +BTRFS_PROGS_CONF_OPTS = --disable-backtrace --disable-zstd --disable-python
> +BTRFS_PROGS_LICENSE = GPL-2.0, LGPL-3.0+ (libbtrfsutil)

Does this means that using the btrfs utilities now requires having a
LGPLv3 library on the target ?

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-04-11  7:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-11  4:45 [Buildroot] [PATCH] btrfs-progs: bump to version 4.16 Baruch Siach
2018-04-11  7:10 ` Thomas Petazzoni [this message]
2018-04-11  7:17   ` Baruch Siach
2018-04-12 21:06 ` Thomas Petazzoni

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=20180411091004.6486eda3@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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.