mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Christian Melki <christian.melki@t2data.com>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: [ptxdist] [PATCH] host-cmake: Version bump. 3.25.3 -> 3.27.0
Date: Sat, 22 Jul 2023 11:03:18 +0000	[thread overview]
Message-ID: <20230722110311.1997307-1-christian.melki@t2data.com> (raw)

As per usual with build tools. Tread lightly.
Doesn't look overly exciting though.
https://cmake.org/cmake/help/latest/release/3.26.html
https://cmake.org/cmake/help/latest/release/3.27.html

* Copyright years changed in license file, cmurl copyright
removed license year (Upstream curl contents).

Signed-off-by: Christian Melki <christian.melki@t2data.com>
---
 rules/host-cmake.make | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/rules/host-cmake.make b/rules/host-cmake.make
index 4e735de87..fcdd40b64 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.25.3
-HOST_CMAKE_MD5		:= 8155fe793c468993ae4614f774826466
+HOST_CMAKE_VERSION	:= 3.27.0
+HOST_CMAKE_MD5		:= a3c5655f96d5c66fa2191909399e2216
 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)
@@ -24,11 +24,11 @@ HOST_CMAKE_SOURCE	:= $(SRCDIR)/$(HOST_CMAKE).$(HOST_CMAKE_SUFFIX)
 HOST_CMAKE_DIR		:= $(HOST_BUILDDIR)/$(HOST_CMAKE)
 HOST_CMAKE_LICENSE	:= 0BSD AND BSD-2-clause AND BSD-3-Clause AND Apache-2.0 AND bzip2-1.0.6 AND (MIT OR public_domain) AND MIT AND curl
 HOST_CMAKE_LICENSE_FILES := \
-	file://Copyright.txt;md5=09069e0fffe4e5eaf6dde04c3b1932e5 \
+	file://Copyright.txt;md5=9d3d12c5f3b4c1f83650adcc65b59c06 \
 	file://Source/kwsys/Copyright.txt;md5=64ed5ec90b0f9868cf0b08ea5b954dfe \
 	file://Utilities/KWIML/Copyright.txt;md5=bdc657917a0eec5751b3d5eafd4b413c \
 	file://Utilities/cmbzip2/LICENSE;md5=1e5cffe65fc786f83a11a4b225495c0b \
-	file://Utilities/cmcurl/COPYING;md5=190c514872597083303371684954f238 \
+	file://Utilities/cmcurl/COPYING;md5=db8448a1e43eb2125f7740fc397db1f6 \
 	file://Utilities/cmexpat/COPYING;md5=9e2ce3b3c4c0f2670883a23bbd7c37a9 \
 	file://Utilities/cmjsoncpp/LICENSE;md5=5d73c165a0f9e86a1342f32d19ec5926 \
 	file://Utilities/cmlibarchive/COPYING;md5=d499814247adaee08d88080841cb5665 \
-- 
2.34.1




             reply	other threads:[~2023-07-22 11:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-22 11:03 Christian Melki [this message]
2023-08-01  7:48 ` [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=20230722110311.1997307-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