[Feature Request] Ship GDRCopy packages in the NVIDIA driver local repository installer
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- c, linux
- Domain
- devops, operating-systems, release
Research direction
No repository files, tests, or entry points are named. Start by locating the release and packaging process that produces nvidia-driver-local-repo--.(deb|rpm), then determine how GDRCopy packages could be included. Done would mean the local repository installers contain compatible GDRCopy packages for supported distributions and driver versions.
Written by the indexing model from the issue text.
Description
Summary
Please consider including the GDRCopy packages in the NVIDIA driver local repository installers
(nvidia-driver-local-repo-<distro>-<version>.(deb|rpm) published under
https://developer.download.nvidia.com/compute/nvidia-driver/<version>/local_installers/).
Motivation
Including GDRCopy alongside the driver in the local repo would let consumers install everything from one source, with cross-compatibility guaranteed by construction.
The driver local repo is already the single, self-contained artifact we use to install the driver and companion packages such as nvidia-fabricmanager.
Having GDRCopy distributed separately has two costs for us:
- Supply chain complexity. Every additional source means separate artifacts to mirror, verify, pin, and track through their lifecycle.
- Compatibility burden. today we must check the cross compatibility between driver/CUDA/GDRCopy, which comes with risks of taking the wrong decision. If GDRCopy shipped inside the driver local repo, each driver release would carry a GDRCopy version validated against it, making the pairing correct by construction.
Thanks for considering it.
- Dominant language
- C
- Stars
- 1.4k
- Forks
- 198
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from NVIDIA/gdrcopy
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Proposal: honor `TMPDIR` in gdrcopy package build scriptsPossibly taken @efegokdemir claimed this 53 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
-
GDRCopy build/installation fails on kernel v6.17 and aboveMay be free again @pakmarkthub claimed this 135 days ago, and no pull request is open. Open
NVIDIA/gdrcopy#335 · 17 comments · 2 reactions · 1 assignee ·
Similar issues
-
SPIDevice selects an active-high device as soon as it is createdPossibly taken @mikeysklar claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
adafruit/circuitpython#11869 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
gnif/LookingGlass#1352 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
bazel-contrib/rules_go#4784 · 1 comment ·
Maintainers usually reply within 1 day