From: Christian Melki <christian.melki@t2data.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH] host-cmake: Version bump. 3.27.4 -> 3.28.3
Date: Tue, 13 Feb 2024 20:22:20 +0100 [thread overview]
Message-ID: <20240213192220.808441-1-christian.melki@t2data.com> (raw)
New minor version. Doesn't look dangerous, but tread lightly.
https://cmake.org/cmake/help/latest/release/3.27.html
https://cmake.org/cmake/help/latest/release/3.28.html
* Fix license file hash. Version and year changed in cmzlib.
Signed-off-by: Christian Melki <christian.melki@t2data.com>
---
rules/host-cmake.make | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/rules/host-cmake.make b/rules/host-cmake.make
index fcd6296ab..0d4788f93 100644
--- a/rules/host-cmake.make
+++ b/rules/host-cmake.make
@@ -15,8 +15,8 @@ HOST_PACKAGES-$(PTXCONF_HOST_CMAKE) += host-cmake
#
# Paths and names
#
-HOST_CMAKE_VERSION := 3.27.4
-HOST_CMAKE_MD5 := 91639a7c786f33340f07a6e0b2a85ee1
+HOST_CMAKE_VERSION := 3.28.3
+HOST_CMAKE_MD5 := 6b16c82b81e1fd80b63bee9696846b21
HOST_CMAKE := cmake-$(HOST_CMAKE_VERSION)
HOST_CMAKE_SUFFIX := tar.gz
HOST_CMAKE_URL := https://cmake.org/files/v$(basename $(HOST_CMAKE_VERSION))/$(HOST_CMAKE).$(HOST_CMAKE_SUFFIX)
@@ -35,7 +35,7 @@ HOST_CMAKE_LICENSE_FILES := \
file://Utilities/cmlibrhash/COPYING;md5=a8c2a557a5c53b1c12cddbee98c099af \
file://Utilities/cmlibuv/LICENSE;md5=ad93ca1fffe931537fcf64f6fcce084d \
file://Utilities/cmnghttp2/COPYING;md5=764abdf30b2eadd37ce47dcbce0ea1ec \
- file://Utilities/cmzlib/Copyright.txt;md5=e08ebeaec41728215e9137e1d2b4d7cd \
+ file://Utilities/cmzlib/Copyright.txt;md5=952d96c4fe88e5ceb8b3a1f9d47b9ec1 \
file://Utilities/cmzstd/LICENSE;md5=c7f0b161edbe52f5f345a3d1311d0b32
--
2.34.1
next reply other threads:[~2024-02-13 19:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 19:22 Christian Melki [this message]
2024-02-14 16:19 ` [ptxdist] [APPLIED] " Michael Olbrich
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=20240213192220.808441-1-christian.melki@t2data.com \
--to=christian.melki@t2data.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