linux/pack.sh: use standard filename format #2239
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
All other platforms use the package filename format: gcm(user)-$RUNTIME-$VERSION.$EXT But the Linux packages have been set to: gcm-$RUNTIME.$VERSION.$EXT Let's standardise on the `.` separator between runtime and version. Signed-off-by: Matthew John Cheetham <mjcheetham@outlook.com>
dscho
approved these changes
Jan 14, 2026
Contributor
dscho
left a comment
dscho
left a comment
There was a problem hiding this comment.
Looks good to me. Let's hope that Hyrum's law doesn't strike and some people actually depend on the old format.
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.
All other platforms use the package filename format:
But the Linux packages have been set to:
Let's standardise on the
.separator between runtime and version.