Repository navigation
Build native Linux packages and publish release downloads automatically - #5
Merged
Merged
Conversation
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
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.
Build installable Debian, RPM and Arch DKMS/app packages in GitHub Actions. PR/main/manual builds upload artifacts; matching version tags publish all package formats, source and SHA256SUMS after the builds succeed.
Use native conffile preservation and lifecycle hooks for module registration, upgrades, removal and optional service resumption. Arch delegates module builds to pacman’s DKMS hooks. Fresh installs do not enable the service. Package installs guard against overwriting standalone/source installations, and the source installer likewise rejects package-managed files.
Document dependency/header requirements and the source-to-native switch. Packages contain DKMS sources; they do not claim kernel-specific precompiled modules or new distro hardware validation.
Validation: all 32 automated tests pass locally, including lifecycle/header/error behavior and Debian control-script syntax. Native build jobs and metadata inspection must pass before merging. Real package installation on Debian/RPM systems remains unvalidated.