From: Alexander Dahl via ptxdist <ptxdist@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Alexander Dahl <ada@thorsis.com>,
Bernhard Sessler <bernhard.sessler@corscience.de>
Subject: [ptxdist] [PATCH] log4cplus: Fix licenses and add license file hash
Date: Mon, 22 Jun 2026 14:48:19 +0200 [thread overview]
Message-ID: <20260622124819.2702603-1-ada@thorsis.com> (raw)
When introduced as package to ptxdist, log4cplus 1.1.0 README already
stated:
> This library is licensed under the Apache Public License 2.0 and two
> clause BSD license. Please read the included LICENSE file for
> details.
Actually some files are under Apache-2.0 and other files are under
BSD-2-Clause, so both apply.
Fixes: 0ac556f6b55d ("log4cplus: Add new package")
Signed-off-by: Alexander Dahl <ada@thorsis.com>
---
Notes:
I actually wrote this patch back in 2019 already. Not sure if I ever
sent it for review, but I double checked it now and it is still correct
for log4cplus 1.2.2 and applies after updating the md5sum of the license
file (which was reformatted between 1.1.0 and 1.2.2 releases).
rules/log4cplus.make | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/rules/log4cplus.make b/rules/log4cplus.make
index 75fdd923a..91d0b8039 100644
--- a/rules/log4cplus.make
+++ b/rules/log4cplus.make
@@ -22,7 +22,8 @@ LOG4CPLUS_SUFFIX := tar.xz
LOG4CPLUS_URL := $(call ptx/mirror, SF, log4cplus/$(LOG4CPLUS).$(LOG4CPLUS_SUFFIX))
LOG4CPLUS_SOURCE := $(SRCDIR)/$(LOG4CPLUS).$(LOG4CPLUS_SUFFIX)
LOG4CPLUS_DIR := $(BUILDDIR)/$(LOG4CPLUS)
-LOG4CPLUS_LICENSE := Apache-2.0
+LOG4CPLUS_LICENSE := Apache-2.0 AND BSD-2-Clause
+LOG4CPLUS_LICENSE_FILES := file://LICENSE;md5=cedaa287ececcb94f9f2880d9c4ef085
# ----------------------------------------------------------------------------
# Prepare
base-commit: 3d185e7c01807e7a2f58a89fe811ed572d267099
--
2.47.3
reply other threads:[~2026-06-22 12:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260622124819.2702603-1-ada@thorsis.com \
--to=ptxdist@pengutronix.de \
--cc=ada@thorsis.com \
--cc=bernhard.sessler@corscience.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