Build and install grimblast from source#1680
Open
hurlbutt wants to merge 1 commit into
Open
Conversation
hurlbutt
referenced
this pull request
Jun 27, 2026
Contributor
Author
|
@mylinuxforwork - To confirm |
Contributor
Author
|
@mylinuxforwork - I saw you released 2.14.0 today. We may need to consider a patch release for this PR if more Fedora and openSUSE users raise bug issues due to an older version of |
1 task
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.
Description
After merging #1650, a user indicated that grimblast on their Fedora installation did not support the
--filenameparameter. Unlike Arch-based installations that usegrimblast-gitfrom the AUR, Fedora and OopenSUSE installations copy a cached (and older) version of the grimblast script into their local bin.We could update the script in this repo, but it wouldn't solve the issue of Fedora and openSUSE users not receiving updates to the script over time (and requiring monitoring of the external repo to know when changes are made). Cloning and building locally would eliminate the need to update the cached version of the script.
Changes
setup/scripts/grimblastgrimblastand installsgrimblastfrom sourcepost-fedora.shandpost-opensuse.shto call new script instead of copying source file into/usr/binHow Has This Been Tested?
I've tested the
clean-install-grimblast.shscript on Arch Linux to confirm it working (after uninstallinggrimblast-gitfrom the AUR). I have not tested this as part of a Fedora or openSUSE installation due to lack of access to those environments. If anyone wants to test on those platforms, it would be appreciated.Checklist
Please ensure your pull request meets the following requirements:
Related Issues
Addresses issues in #1650
Additional Notes
If we want to pin
grimblastto a specific commit versus always using main for stability reasons, we can update the script to checkout that specific commit before building/installing.