From: Quentin Schulz <quentin.schulz@cherry.de>
To: peter.kjellerstedt@axis.com, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] util-linux: Improve the package licenses
Date: Tue, 3 Jun 2025 11:27:23 +0200 [thread overview]
Message-ID: <166b439a-86cd-4bef-816f-c016732236da@cherry.de> (raw)
In-Reply-To: <20250603031425.2206714-1-pkj@axis.com>
Hi Peter,
On 6/3/25 5:14 AM, Peter Kjellerstedt via lists.openembedded.org wrote:
> The default license for util-linux is GPL-2.0-or-later.
>
> Most of the applications and the libraries are also linked with
> libcommon.la, which uses these licenses:
> LGPL-2.1-or-later & BSD-2-Clause & BSD-3-Clause & MIT
>
> Set the above licenses for all dynamic packages, unless explicitly
> specified.
>
> In particular, this avoids setting BSD-4-Clause-UC and EUPL-1.2 on
> packages where they do not belong.
>
> License-Update: See above
> Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
> ---
> meta/recipes-core/util-linux/util-linux.inc | 41 ++++++++++++++++---
> .../util-linux/util-linux_2.41.bb | 3 ++
> 2 files changed, 38 insertions(+), 6 deletions(-)
>
> diff --git a/meta/recipes-core/util-linux/util-linux.inc b/meta/recipes-core/util-linux/util-linux.inc
> index b0f2a9d497..bd7ad10035 100644
> --- a/meta/recipes-core/util-linux/util-linux.inc
> +++ b/meta/recipes-core/util-linux/util-linux.inc
> @@ -6,14 +6,43 @@ disk partitioning, kernel message management, filesystem creation, and system lo
>
> SECTION = "base"
>
> +# Most of the applications and the libraries are linked with libcommon.la,
> +# which uses these licenses
Is this something we can detect directly within the binaries in a
package, so that we could simply add those licenses dynamically to
LICENSE:${PN}-x instead of having to list them by hand?
Packages without a package-specific LICENSE will take the recipe's
LICENSE I believe, considering that *.la is part of the -dev package
should the -dev package have a "more precise" license than the recipe's
default?
Cheers,
Quentin
next prev parent reply other threads:[~2025-06-03 9:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-03 3:14 [PATCH] util-linux: Improve the package licenses Peter Kjellerstedt
2025-06-03 9:27 ` Quentin Schulz [this message]
2025-06-03 10:07 ` [OE-core] " Peter Kjellerstedt
2025-06-03 10:12 ` Quentin Schulz
2025-06-03 10:32 ` Peter Kjellerstedt
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=166b439a-86cd-4bef-816f-c016732236da@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.kjellerstedt@axis.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