Github messages for voidlinux
 help / color / mirror / Atom feed
From: bvdeenen <bvdeenen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] cmake: update to 3.31.3
Date: Mon, 30 Dec 2024 19:59:19 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-53766@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 855 bytes --]

There is a new pull request by bvdeenen against master on the void-packages repository

https://github.com/bvdeenen/void-packages master
https://github.com/void-linux/void-packages/pull/53766

cmake: update to 3.31.3
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **briefly**
- a warning with FetchContent that shows with the previous cmake 3.30 version no longer shows. I've tested with CPM and a lot of dependencies and includes and it seems to work fine.

#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC) x86-84, libc
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - none



A patch file from https://github.com/void-linux/void-packages/pull/53766.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-master-53766.patch --]
[-- Type: text/x-diff, Size: 1098 bytes --]

From bea62273439392c19ca8389a5dfcea5599fa9f9c Mon Sep 17 00:00:00 2001
From: Bart van Deenen <bartvandeenen@streammachine.io>
Date: Mon, 30 Dec 2024 19:54:05 +0100
Subject: [PATCH] cmake: update to 3.31.3

---
 srcpkgs/cmake/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/cmake/template b/srcpkgs/cmake/template
index 1b6b23cf3dc8cc..20ba23b0289df7 100644
--- a/srcpkgs/cmake/template
+++ b/srcpkgs/cmake/template
@@ -1,6 +1,6 @@
 # Template file for 'cmake'
 pkgname=cmake
-version=3.30.1
+version=3.31.3
 revision=1
 build_style=cmake
 configure_args="-DCMAKE_DOC_DIR=/share/doc/cmake
@@ -17,7 +17,7 @@ maintainer="Đoàn Trần Công Danh <congdanhqx@gmail.com>"
 license="BSD-3-Clause, ICU"
 homepage="https://www.cmake.org"
 distfiles="https://www.cmake.org/files/v${version%.*}/${pkgname}-${version}.tar.gz"
-checksum=df9b3c53e3ce84c3c1b7c253e5ceff7d8d1f084ff0673d048f260e04ccb346e1
+checksum=fac45bc6d410b49b3113ab866074888d6c9e9dc81a141874446eb239ac38cb87
 
 if [ "$XBPS_TARGET_LIBC" = musl ]; then
 	configure_args+=" -DCMake_NO_SELF_BACKTRACE=1"

             reply	other threads:[~2024-12-30 18:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-30 18:59 bvdeenen [this message]
2024-12-30 20:40 ` bvdeenen
2024-12-30 20:41 ` bvdeenen
2024-12-30 20:51 ` bvdeenen
2024-12-31  3:33 ` classabbyamp
2024-12-31 10:32 ` bvdeenen
2024-12-31 10:35 ` bvdeenen
2024-12-31 10:37 ` bvdeenen
2024-12-31 10:39 ` bvdeenen
2025-01-08 13:16 ` bvdeenen
2025-01-08 14:46 ` bvdeenen
2025-01-09 16:29 ` [PR PATCH] [Closed]: " bvdeenen
2025-01-09 16:29 ` bvdeenen

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-53766@inbox.vuxu.org \
    --to=bvdeenen@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /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;
as well as URLs for NNTP newsgroup(s).