hedge-dev / hedge-dev/UnleashedRecomp
Add version info to Flatpak's .metainfo.xml
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 5.1k
- Forks
- 421
- PR merge metrics
- No merged PRs in 30d
Description
Validation
- I have checked the Issues page to see if my problem has already been reported
- I have confirmed that this bug does not occur in the original game running on original Xbox 360 hardware
If you have DLC installed, please specify which ones you have.
- Apotos & Shamar Adventure Pack
- Chun-nan Adventure Pack
- Empire City & Adabat Adventure Pack
- Holoska Adventure Pack
- Mazuri Adventure Pack
- Spagonia Adventure Pack
If you have mods enabled, please specify which ones you have.
No response
If you have codes enabled, please specify which ones you have.
No response
Describe the Bug
Currently the version number isn't shown because the release data is not present in .metainfo.xml
This can be fixed by adding the release info from the AppStream sprecification.
This is the specification: https://www.freedesktop.org/software/appstream/docs/sect-Metadata-Releases.html
It should be enough to have one entry with the version number and release date for all version in reverse chronological order
Steps to Reproduce
- Run flatpak list
- Notice how the flatpak has a empty version field
- Run flatpak info
- Notice again how there will be not version data
- Visit KDE Discover or GNOME Software
- Notice how it has no version info
Expected Behavior
Assuming the release data is set correctly with the release info for 1.0.0, 1.0.1 and 1.0.2 and all newer versions, flatpak CLI tooling would extract the version from the metadata and the version number would also be shown in any Linux frontend app store.
Footage
N/A. Flatpak-specific
System Specifications
Not very relevant. However a Steam Deck OLED using SteamOS was used.
Additional Context
This is specific to the Flatpak integration with the system and is minor, however this will usually let the user know which version is currently installed (whih is not possible right now) or which version will be installed (although I'm not very sure)
Contributor guide
No contributing guide indexed for this repository
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
Find the repository's Flatpak .metainfo.xml and read the AppStream Metadata Releases specification linked in the issue. Check the existing metadata, then validate with flatpak list and flatpak info and a Linux app-store frontend; done means release entries expose the installed version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- xml
- Domain
- release
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100