linuxmint / linuxmint/mintupdate
Better describe Flatpak package versions
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 425
- Forks
- 190
- PR merge metrics
- No merged PRs in 30d
Description
Is your feature request related to a problem? Please describe.
Platform runtimes are often installed with multiple versions, each support different Flatpak applications. When they are subjected to update, the GUI interface looks as if the same package is being updated twice.
Describe the solution you'd like
Show extra version details so that they are more clear, not just a gibberish hash value
Describe alternatives you've considered
If one run flatpak list in terminal, one can see meaningful version numbers that distinguish their differences. Below is an extract of what shown in my computer (with what I actually installed left out)
Name Application ID Version Branch Installation
Freedesktop Platform org.freedesktop.Platform 21.08.17.1 21.08 system
Freedesktop Platform org.freedesktop.Platform 22.08.5 22.08 system
Mesa org.freedesktop.Platform.GL.default 21.3.9 21.08 system
Mesa org.freedesktop.Platform.GL.default 22.3.2 22.08 system
Mesa (Extra) org.freedesktop.Platform.GL.default 22.3.2 22.08-extra system
openh264 org.freedesktop.Platform.openh264 19.08 system
openh264 org.freedesktop.Platform.openh264 2.1.0 2.0 system
openh264 org.freedesktop.Platform.openh264 2.1.0 2.2.0 system
KDE Application Platform org.kde.Platform 5.15-21.08 system
KDE Application Platform org.kde.Platform 5.15-22.08 system
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
No source files, tests, or entry points are named. Start by tracing how Flatpak packages are listed and rendered in the Update Manager, then compare the available version and branch metadata with the terminal output described here. Done means distinct installed runtime versions have readable details instead of only hash-like values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, python
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100