From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Roland Hieber <rhi@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] libtracefs: fix license and add license files
Date: Mon, 27 Jan 2025 09:35:04 +0100 [thread overview]
Message-ID: <20250127083504.362582-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20250117104113.176520-1-rhi@pengutronix.de>
Thanks, applied as c0a1a0dd425ccb075b272bf984849bac70abe0d0.
Michael
[sent from post-receive hook]
On Mon, 27 Jan 2025 09:35:04 +0100, Roland Hieber <rhi@pengutronix.de> wrote:
> While the source includes a GPL-2.0 license text, this license is only
> used for the build scripts, and does not make it into the binary. The
> Bison-generated parser code is licensed under GPL-3.0-or-later with a
> license exception allowing it (in this case) to be released under
> a different license. The resulting binary is under LGPL-2.1-or-later (as
> mentioned in the original mail thread it uses the old SPDX identifiers).
>
> Link: https://lore.ptxdist.org/ptxdist/Z4DbKik6UoE956Sq@pengutronix.de
> Signed-off-by: Roland Hieber <rhi@pengutronix.de>
> Message-Id: <20250117104113.176520-1-rhi@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/libtracefs.make b/rules/libtracefs.make
> index 23fe43c4b741..5282fc8ede13 100644
> --- a/rules/libtracefs.make
> +++ b/rules/libtracefs.make
> @@ -21,10 +21,13 @@ LIBTRACEFS_SUFFIX := tar.xz
> LIBTRACEFS_URL := https://git.kernel.org/pub/scm/libs/libtrace/libtracefs.git;tag=libtracefs-$(LIBTRACEFS_VERSION)
> LIBTRACEFS_SOURCE := $(SRCDIR)/$(LIBTRACEFS).$(LIBTRACEFS_SUFFIX)
> LIBTRACEFS_DIR := $(BUILDDIR)/$(LIBTRACEFS)
> -LIBTRACEFS_LICENSE := LGPL-2.1-only AND GPL-2.0-only
> -LIBTRACEFS_LICENSE_FILES := \
> - file://LICENSES/LGPL-2.1;md5=b370887980db5dd40659b50909238dbd \
> - file://LICENSES/GPL-2.0;md5=e6a75371ba4d16749254a51215d13f97
> +LIBTRACEFS_LICENSE := LGPL-2.1-only AND GPL-3.0-or-later WITH Bison-exception-2.2
> +LIBTRACEFS_LICENSE_FILES := \
> + file://src/tracefs-utils.c;startline=1;endline=8;md5=c6bedd276596b669012b69e9317ffade \
> + file://src/sqlhist.tab.c;startline=3;endline=32;md5=67ac50d80b3ebb72edad40dafe30d75e \
> + file://LICENSES/LGPL-2.1;md5=b370887980db5dd40659b50909238dbd
> +# note: source tarball includes a LICENSES/GPL-2.0, but it's only used for
> +# build scripts. GPL-3.0 text is missing.
>
> # ----------------------------------------------------------------------------
> # Prepare
prev parent reply other threads:[~2025-01-27 8:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 10:43 [ptxdist] [PATCH] " Roland Hieber
2025-01-17 8:47 ` Michael Olbrich
2025-01-17 10:41 ` [ptxdist] [PATCH v2] " Roland Hieber
2025-01-27 8:35 ` Michael Olbrich [this message]
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=20250127083504.362582-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
--cc=rhi@pengutronix.de \
/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