AppImage should receive better version number
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 16.2k
- Forks
- 1.9k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 80
Description
Currently, only a git hash is embedded as a version number. Git hashs are not version numbers, at most I can tell two different AppImages apart, but they're not monotonic and have no relation to the version number displayed e.g., inside the game.
By calling export VERSION=... before calling linuxdeploy/appimagetool you can embed a proper version number. This is a common pattern for making AppImages:
> export VERSION=$(git describe --tags)
> ./linuxdeploy-*.AppImage ...
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the Linux AppImage packaging flow that invokes linuxdeploy and appimagetool; the issue does not name a specific file or test. Trace how the current Git hash becomes the embedded version, then verify that exporting VERSION from git describe --tags produces a proper version in the generated AppImage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, shell
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100