Github messages for voidlinux
 help / color / mirror / Atom feed
From: motorto <motorto@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] imath: update to 3.1.10.
Date: Sun, 25 Feb 2024 19:28:34 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48938@inbox.vuxu.org> (raw)

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

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

https://github.com/motorto/void-packages imath-3.1.10
https://github.com/void-linux/void-packages/pull/48938

imath: update to 3.1.10.
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **briefly**

#### Local build testing
- I built this PR locally for my native architecture, x86_64-glibc

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

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

From 2ca37870a2d71218b293f60f02f9245498aa5cf4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Andr=C3=A9=20Cerqueira?= <acerqueira021@gmail.com>
Date: Sun, 25 Feb 2024 18:27:55 +0000
Subject: [PATCH] imath: update to 3.1.10.

---
 .../patches/split-pyimath-cmake-target.patch  | 39 -------------------
 srcpkgs/imath/template                        |  6 +--
 2 files changed, 3 insertions(+), 42 deletions(-)
 delete mode 100644 srcpkgs/imath/patches/split-pyimath-cmake-target.patch

diff --git a/srcpkgs/imath/patches/split-pyimath-cmake-target.patch b/srcpkgs/imath/patches/split-pyimath-cmake-target.patch
deleted file mode 100644
index 94d8b9ca65ccfd..00000000000000
--- a/srcpkgs/imath/patches/split-pyimath-cmake-target.patch
+++ /dev/null
@@ -1,39 +0,0 @@
---- a/config/ImathConfig.cmake.in
-+++ b/config/ImathConfig.cmake.in
-@@ -4,4 +4,7 @@
- @PACKAGE_INIT@
- 
- include("${CMAKE_CURRENT_LIST_DIR}/@PROJECT_NAME@Targets.cmake")
-+if(EXISTS "${CMAKE_CURRENT_LIST_DIR}/PyImathTargets.cmake")
-+  include("${CMAKE_CURRENT_LIST_DIR}/PyImathTargets.cmake")
-+endif()
- check_required_components("@PROJECT_NAME@")
---- a/src/python/config/ModuleDefine.cmake
-+++ b/src/python/config/ModuleDefine.cmake
-@@ -52,7 +52,7 @@ function(PYIMATH_ADD_LIBRARY_PRIV libnam
-   add_library(${PROJECT_NAME}::${libname} ALIAS ${libname})
- 
-   install(TARGETS ${libname}
--    EXPORT ${PROJECT_NAME}
-+    EXPORT PyImath
-     RUNTIME DESTINATION ${CMAKE_INSTALL_BINDIR}
-     LIBRARY DESTINATION ${CMAKE_INSTALL_LIBDIR}
-     ARCHIVE DESTINATION ${CMAKE_INSTALL_LIBDIR}
---- a/src/python/config/CMakeLists.txt
-+++ b/src/python/config/CMakeLists.txt
-@@ -7,8 +7,14 @@
- add_library(PyImathConfig INTERFACE)
- target_include_directories(PyImathConfig INTERFACE
-   $<BUILD_INTERFACE:${CMAKE_CURRENT_BINARY_DIR}>)
--install(TARGETS PyImathConfig EXPORT ${PROJECT_NAME})
-+install(TARGETS PyImathConfig EXPORT PyImath)
- add_library(PyImath::Config ALIAS PyImathConfig)
-+install(EXPORT PyImath
-+  DESTINATION ${CMAKE_INSTALL_LIBDIR}/cmake/PyImath
-+  FILE PyImathTargets.cmake
-+  NAMESPACE Imath::
-+  EXPORT_LINK_INTERFACE_LIBRARIES
-+)
- 
- if(IMATH_INSTALL_PKG_CONFIG)
-   # use a helper function to avoid variable pollution, but pretty simple
diff --git a/srcpkgs/imath/template b/srcpkgs/imath/template
index b4a47b59073b8c..8638655925543a 100644
--- a/srcpkgs/imath/template
+++ b/srcpkgs/imath/template
@@ -1,7 +1,7 @@
 # Template file for 'imath'
 pkgname=imath
-version=3.1.9
-revision=3
+version=3.1.10
+revision=1
 build_style=cmake
 configure_args="-DPYTHON=ON"
 hostmakedepends="python3-numpy"
@@ -12,7 +12,7 @@ license="BSD-3-Clause"
 homepage="https://imath.readthedocs.io/"
 changelog="https://raw.githubusercontent.com/AcademySoftwareFoundation/Imath/main/CHANGES.md"
 distfiles="https://github.com/AcademySoftwareFoundation/Imath/archive/v${version}/imath-${version}.tar.gz"
-checksum=f1d8aacd46afed958babfced3190d2d3c8209b66da451f556abd6da94c165cf3
+checksum=f2943e86bfb694e216c60b9a169e5356f8a90f18fbd34d7b6e3450be14f60b10
 
 if [ "$XBPS_CHECK_PKGS" ]; then
 	configure_args+=" -DBUILD_TESTING=ON"

             reply	other threads:[~2024-02-25 18:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-25 18:28 motorto [this message]
2024-02-25 19:02 ` [PR PATCH] [Closed]: " motorto
2024-02-25 23:52 ` melroy89
2024-02-26  9:38 ` motorto

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-48938@inbox.vuxu.org \
    --to=motorto@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).