dev-python/librmm
RAPIDS Memory Manager — C++ library (librmm)
Screenshots
View
Download
BrowseChangeLog
commit f6c86781439d264beab537cac242d7e244c54296
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu Oct 8 15:11:09 2026 +0200
dev-python/librmm: add 26.10.0
Upstream moved to rapids-logger 0.3, which the exact pin follows.
commit 496caa710882caf5f30471b0aad6c90b10c02dc2
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu Oct 8 00:28:01 2026 +0200
dev-python/librmm: pin rapids-cmake and drop PROPERTIES=live
rmm checks rapids-cmake out from its moving release/26.06 and
release/26.08 branches, so the CPM versions it pulls could change
after release. Fetch the matching v26.06.00/v26.08.00 tag as a
distfile instead; that rapids-cmake pins CCCL and NVTX to commit
archives with SHA256 hashes.
The marker goes with it: RESTRICT=network-sandbox already grants the
configure-time network access CPM needs.
PROPERTIES=live marks source that varies between installs, as VCS
ebuilds do. On a release it put the package in @live-rebuild and
exempted it from pkgcheck's modified-ebuild, DroppedKeywords and
RedundantVersion checks.
commit e66eb579f9d3e494feef68aeac74261d8764d45c
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sat Oct 3 23:23:55 2026 +0200
dev-python/librmm: drop the PyPI references
PyPI has no librmm project, only the librmm-cu12 and librmm-cu13
wheels, so the pypi remote-id and the PyPI HOMEPAGE pointed nowhere.
The ebuilds build from the GitHub source, which stays.
commit 8622b22cd38c025437b154d74f46001a0ef0e82d
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu Sep 10 04:06:42 2026 +0200
dev-python/librmm: trim 26.6.0 comment prose
commit 120a354a2cc7f84056ae53377e0987814f623d77
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu Sep 10 04:06:11 2026 +0200
dev-python/librmm: trim 26.8.0 comment prose
commit 568c1f7d0251e93e380b084931108924d2c875dc
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Fri Aug 14 17:44:53 2026 +0200
dev-python/librmm: enforce upstream build floors
RAPIDS 26.08 requires CMake 4 and scikit-build-core 0.11 or newer after the
documented backend substitution. Declare both floors so the selected build toolchain
satisfies the shipped CMake and pyproject metadata.
commit 29e76e659d83ad79dd35ec7c6cb4656da9a55b38
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu Aug 6 17:52:53 2026 +0200
dev-python/librmm: add 26.8.0
Coordinated RAPIDS 26.08 bump; rapids-cmake CPM branch moves to branch-26.08 and upstream still pins rapids-logger==0.2.*, so the ~rapids-logger-0.2.3 dep is unchanged.
commit d6e6ed95596ae118917309d3468f99274ce945af
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Wed Jun 10 17:58:32 2026 +0200
dev-python/librmm: new package, add 26.6.0
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu Oct 8 15:11:09 2026 +0200
dev-python/librmm: add 26.10.0
Upstream moved to rapids-logger 0.3, which the exact pin follows.
commit 496caa710882caf5f30471b0aad6c90b10c02dc2
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu Oct 8 00:28:01 2026 +0200
dev-python/librmm: pin rapids-cmake and drop PROPERTIES=live
rmm checks rapids-cmake out from its moving release/26.06 and
release/26.08 branches, so the CPM versions it pulls could change
after release. Fetch the matching v26.06.00/v26.08.00 tag as a
distfile instead; that rapids-cmake pins CCCL and NVTX to commit
archives with SHA256 hashes.
The marker goes with it: RESTRICT=network-sandbox already grants the
configure-time network access CPM needs.
PROPERTIES=live marks source that varies between installs, as VCS
ebuilds do. On a release it put the package in @live-rebuild and
exempted it from pkgcheck's modified-ebuild, DroppedKeywords and
RedundantVersion checks.
commit e66eb579f9d3e494feef68aeac74261d8764d45c
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sat Oct 3 23:23:55 2026 +0200
dev-python/librmm: drop the PyPI references
PyPI has no librmm project, only the librmm-cu12 and librmm-cu13
wheels, so the pypi remote-id and the PyPI HOMEPAGE pointed nowhere.
The ebuilds build from the GitHub source, which stays.
commit 8622b22cd38c025437b154d74f46001a0ef0e82d
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu Sep 10 04:06:42 2026 +0200
dev-python/librmm: trim 26.6.0 comment prose
commit 120a354a2cc7f84056ae53377e0987814f623d77
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu Sep 10 04:06:11 2026 +0200
dev-python/librmm: trim 26.8.0 comment prose
commit 568c1f7d0251e93e380b084931108924d2c875dc
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Fri Aug 14 17:44:53 2026 +0200
dev-python/librmm: enforce upstream build floors
RAPIDS 26.08 requires CMake 4 and scikit-build-core 0.11 or newer after the
documented backend substitution. Declare both floors so the selected build toolchain
satisfies the shipped CMake and pyproject metadata.
commit 29e76e659d83ad79dd35ec7c6cb4656da9a55b38
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu Aug 6 17:52:53 2026 +0200
dev-python/librmm: add 26.8.0
Coordinated RAPIDS 26.08 bump; rapids-cmake CPM branch moves to branch-26.08 and upstream still pins rapids-logger==0.2.*, so the ~rapids-logger-0.2.3 dep is unchanged.
commit d6e6ed95596ae118917309d3468f99274ce945af
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Wed Jun 10 17:58:32 2026 +0200
dev-python/librmm: new package, add 26.6.0