feat(install): add rpm dev installer support#1262
Merged
maxamillion merged 1 commit intomainfrom May 8, 2026
Merged
Conversation
drew
requested review from
a team,
derekwaynecarr,
maxamillion and
mrunalp
as code owners
drew
force-pushed
the
rpm-to-install-script
branch
from
ad98fca to
d331a35
Compare
Signed-off-by: Drew Newberry <anewberry@nvidia.com>
drew
force-pushed
the
rpm-to-install-script
branch
from
d331a35 to
772cc7f
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
Add RPM package support to install-dev.sh so RPM-family Linux hosts can install dev and tagged releases with the same checksum verification flow as Debian hosts.
Related Issue
N/A
Changes
Testing
Note: mise run pre-commit completed Rust format, clippy, check, Rust tests, markdown lint, Helm lint, and license checks successfully, but the aggregate command exited failed because python:proto started while .venv was being recreated and could not import grpc_tools. Running mise run python:proto immediately afterward passed.
Checklist