Update on every build the git hash shown by rizin -v
#2863
Merged
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.
Your checklist for this pull request
Detailed description
This pr updates on every build the git commit hash shown by
rizin -v
. Previously, the updating was done only on a meson configure, which doesn't happen on every commit and thus the git commit hash shown can sometimes be out-of-date.Currently Python is used for the updating of the
gittip
file containing the commit hash. This shouldn't be too much of a burden though since Python is needed for meson and therefore should be in the cache.Test plan
After this code is installed, add a new commit that doesn't cause build file regeneration. The commit hash shown by
rizin -v
should be the hash of the new commit. All builds are green.Closing issues
...