Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Perale via buildroot <buildroot@buildroot.org>
To: Fiona Klute <fiona.klute@gmx.de>
Cc: Thomas Perale <thomas.perale@mind.be>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/4] package/dbus-broker: clarify license information
Date: Fri, 31 Jul 2026 14:05:14 +0200	[thread overview]
Message-ID: <20260731120514.3440-1-thomas.perale@mind.be> (raw)
In-Reply-To: <20260720170437.133823-2-fiona.klute@gmx.de>

In reply of:
> All these bundled subprojects explicitly give "Apache-2.0 OR
> LGPL-2.1-or-later" in their README.md files.
> 
> Signed-off-by: Fiona Klute (Othermo GmbH) <fiona.klute@gmx.de>

Applied to 2025.02.x & 2026.05.x. Thanks

> ---
> Note that the dbus-broker "main" branch has changed its license to
> GPL-3.0-or-later, DBUS_BROKER_LICENSE describes the packaged v37 (latest
> release).
> 
>  package/dbus-broker/dbus-broker.mk | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/package/dbus-broker/dbus-broker.mk b/package/dbus-broker/dbus-broker.mk
> index 7e029879f9..869eec462b 100644
> --- a/package/dbus-broker/dbus-broker.mk
> +++ b/package/dbus-broker/dbus-broker.mk
> @@ -10,7 +10,7 @@ DBUS_BROKER_SITE = https://github.com/bus1/dbus-broker/releases/download/v$(DBUS
>  
>  DBUS_BROKER_LICENSE = \
>  	Apache-2.0, \
> -	Apache-2.0 and/or LGPL-2.1+ (c-dvar, c-ini, c-list, c-rbtree, c-shquote, c-stdaux, c-utf8)
> +	Apache-2.0 or LGPL-2.1+ (bundled subprojects c-dvar, c-ini, c-list, c-rbtree, c-shquote, c-stdaux, c-utf8)
>  # For the third-party code, the licensing legal-info is inconsistent between
>  # the AUTHORS and README, so keep both
>  DBUS_BROKER_LICENSE_FILES = \
> -- 
> 2.53.0
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2026-07-31 12:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-20 17:04 [Buildroot] [PATCH 1/4] package/python-paho-mqtt: clarify license information Fiona Klute via buildroot
2026-07-20 17:04 ` [Buildroot] [PATCH 2/4] package/dbus-broker: " Fiona Klute via buildroot
2026-07-31 12:05   ` Thomas Perale via buildroot [this message]
2026-07-20 17:04 ` [Buildroot] [PATCH 3/4] package/nettle: clarify license info Fiona Klute via buildroot
2026-07-31 12:05   ` Thomas Perale via buildroot
2026-07-20 17:04 ` [Buildroot] [PATCH 4/4] package/busybox: use SPDX license identifier for bzip2 license Fiona Klute via buildroot
2026-07-31 12:05   ` Thomas Perale via buildroot
2026-07-20 20:16 ` [Buildroot] [PATCH 1/4] package/python-paho-mqtt: clarify license information Julien Olivain via buildroot
2026-07-31 12:05 ` Thomas Perale via buildroot

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=20260731120514.3440-1-thomas.perale@mind.be \
    --to=buildroot@buildroot.org \
    --cc=fiona.klute@gmx.de \
    --cc=thomas.perale@mind.be \
    /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