From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Alexander Dahl <ada@thorsis.com>
Subject: Re: [ptxdist] [APPLIED] log4cplus: Fix licenses and add license file hash
Date: Thu, 25 Jun 2026 21:23:39 +0200 [thread overview]
Message-ID: <20260625192339.832811-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20260622124819.2702603-1-ada@thorsis.com>
Thanks, applied as 6e5f040f189917516df6bbe694f48b0e40129055.
Michael
[sent from post-receive hook]
On Thu, 25 Jun 2026 21:23:39 +0200, Alexander Dahl <ada@thorsis.com> wrote:
> 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>
> Message-Id: <20260622124819.2702603-1-ada@thorsis.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/log4cplus.make b/rules/log4cplus.make
> index 75fdd923a0ed..91d0b8039a1d 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
prev parent reply other threads:[~2026-06-25 19:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-22 12:48 [ptxdist] [PATCH] " Alexander Dahl via ptxdist
2026-06-25 19:23 ` 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=20260625192339.832811-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ada@thorsis.com \
--cc=ptxdist@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