From: dataCobra <dataCobra@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] nvidia: update to 545.29.06.
Date: Fri, 19 Jan 2024 19:00:39 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48286@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 647 bytes --]
There is a new pull request by dataCobra against master on the void-packages repository
https://github.com/dataCobra/void-packages nvidia
https://github.com/void-linux/void-packages/pull/48286
nvidia: update to 545.29.06.
#### Testing the changes
- I tested the changes in this PR: **YES**
Using it for more than a month now.
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
This is the version from the new feature branch. The question is, do we want to switch branches to the new feature branch?
A patch file from https://github.com/void-linux/void-packages/pull/48286.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-nvidia-48286.patch --]
[-- Type: text/x-diff, Size: 2597 bytes --]
From 5244c65f072734790941ef9e0d84ec1ee97a9c57 Mon Sep 17 00:00:00 2001
From: dataCobra <datacobra@thinkbot.de>
Date: Fri, 19 Jan 2024 18:36:42 +0100
Subject: [PATCH] nvidia: update to 545.29.06.
---
srcpkgs/nvidia/template | 20 ++++++++++----------
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/srcpkgs/nvidia/template b/srcpkgs/nvidia/template
index 64fb7dcec8e0e..f9c6b8acf1552 100644
--- a/srcpkgs/nvidia/template
+++ b/srcpkgs/nvidia/template
@@ -3,7 +3,7 @@
_desc="NVIDIA drivers for linux"
pkgname=nvidia
-version=535.146.02
+version=545.29.06
revision=1
maintainer="Andrew Benson <abenson+void@gmail.com>"
license="custom:NVIDIA Proprietary"
@@ -19,7 +19,7 @@ conflicts="xserver-abi-video>25_1 nvidia470>=0 nvidia390>=0"
_pkg="NVIDIA-Linux-x86_64-${version}"
distfiles="http://uk.download.nvidia.com/XFree86/Linux-x86_64/${version}/${_pkg}.run"
-checksum=49fd1cc9e445c98b293f7c66f36becfe12ccc1de960dfff3f1dc96ba3a9cbf70
+checksum=82bc55676add43416c146e70c624c8dc6af16cc04c7238680c56a30e0045b17b
# subpackages need to be processed in this specific order
subpackages="nvidia-gtklibs nvidia-dkms nvidia-firmware nvidia-opencl nvidia-libs nvidia-libs-32bit"
depends="nvidia-libs-${version}_${revision}
@@ -100,6 +100,12 @@ _install_libs() {
${DESTDIR}/${libdir}/libnvidia-allocator.so.1
ln -sf libnvidia-allocator.so.1 \
${DESTDIR}/${libdir}/libnvidia-allocator.so
+
+ vinstall libnvidia-gpucomp.so.${version} 755 ${libdir}
+ ln -sf libnvidia-gpucomp.so.${version} \
+ ${DESTDIR}/${libdir}/libnvidia-gpucomp.so.1
+ ln -sf libnvidia-gpucomp.so.1 \
+ ${DESTDIR}/${libdir}/libnvidia-gpucomp.so
}
do_extract() {
@@ -129,8 +135,8 @@ do_install() {
${DESTDIR}/usr/lib/nvidia/xorg/libglxserver_nvidia.so.1
# Wayland/GBM
- vinstall libnvidia-egl-wayland.so.1.1.11 755 usr/lib
- ln -sf libnvidia-egl-wayland.so.1.1.11 \
+ vinstall libnvidia-egl-wayland.so.1.1.12 755 usr/lib
+ ln -sf libnvidia-egl-wayland.so.1.1.12 \
${DESTDIR}/usr/lib/libnvidia-egl-wayland.so.1
vinstall libnvidia-egl-gbm.so.1.1.0 755 usr/lib
ln -sf libnvidia-egl-gbm.so.1.1.0 \
@@ -219,12 +225,6 @@ do_install() {
# vulkan real-time ray tracing extensions
vinstall libnvidia-rtcore.so.${version} 755 usr/lib
- vinstall libnvidia-vulkan-producer.so.${version} 755 usr/lib
- ln -sf libnvidia-vulkan-producer.so.${version} \
- ${DESTDIR}/usr/lib/libnvidia-vulkan-producer.so
- ln -sf libnvidia-vulkan-producer.so.${version} \
- ${DESTDIR}/usr/lib/libnvidia-vulkan-producer.so.1
-
# ngx
vbin nvidia-ngx-updater
vinstall libnvidia-ngx.so.${version} 755 usr/lib
next reply other threads:[~2024-01-19 18:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 18:00 dataCobra [this message]
2024-01-20 2:44 ` classabbyamp
2024-01-20 5:20 ` abenson
2024-01-20 7:52 ` dataCobra
2024-01-31 15:35 ` [PR PATCH] [Closed]: " ahesford
-- strict thread matches above, loose matches on Subject: below --
2023-12-29 5:58 [PR PATCH] " CODJointOps
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-48286@inbox.vuxu.org \
--to=datacobra@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).