feat: Split nvidia-open-dkms into its own package #534
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
https://download.nvidia.com/XFree86/NVIDIA-kernel-module-source/ We could also consider to use this, since there is a available checksum. |
Historically, NVIDIA's open kernel module GitHub repository has been lagging behind its runfile driver. This has happened already for atleast 2 versions now, and it's uncertain whether or not their release model will improve for future releases. Signed-off-by: Eric Naim <[email protected]>
Since nvidia-open-dkms has been split into its own package, package kernel-open from runfile in this PKGBUILD for posterity. This is disabled by default because the package sourced from the GitHub repository is preferred. Signed-off-by: Eric Naim <[email protected]>
Now that each dkms.conf file is identical, we can simplify how we edit each dkms.conf by using find instead of editting each of them in two different stages. Co-Authored-by: Vasiliy Stelmachenok <[email protected]> Signed-off-by: Eric Naim <[email protected]> Signed-off-by: Vasiliy Stelmachenok <[email protected]>
1Naim
force-pushed
the
feat/nvidia-split-dkms
branch
from
8ae9642 to
d061967
Compare
Seems perfect actually, it looks like it's also pushed a few days before the driver release announcement (atleast for the current latest, I'll check past versions at a later time). |
1Naim
added a commit
that referenced
this pull request
Feb 28, 2025
This tarball was brought to my attention by Peter in #534. At first glance, these tarballs are pushed several days before NVIDIA makes their driver release announcement, and far earlier than what is pushed to GitHub. These sources are preferred over the GitHub sources because it is released earlier. Checksums are switched from sha512 to sha256 because the checksums provided by NVIDIA are sha256. No functional changes intended. Signed-off-by: Eric Naim <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Historically, NVIDIA's open kernel module GitHub repository has been lagging behind its runfile driver.
This has happened already for atleast 2 versions now, and it's uncertain whether or not their release model
will improve for future releases.|
This PR splits the open kernel module sourced from GitHub into its own package so it doesn't block users and/or packagers from updating the userspace drivers. Note that
nvidia-utilsnow also supports packaging the open modules sourced from the runfile, although it is disabled by default to prefer the Github-sourced modules during packaging.