[PATCH] AppStream IDs differ between appdata.xml file and Flatpak metadata
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Inkscape |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Inkscape's Appstream ID on Flathub is "org.inkscape.
But Inkscape's appdata.xml file uses a different AppStream ID: "inkscape.desktop" (https:/
This causes problems. The point of Appstream IDs is that each app has a unique one; if the same app has different Appstream IDs in different distribution channels, then they'll confusingly show up as different apps in clients that can display content from multiple sources, such as GNOME Software Center and KDE Discover. Here's what it looks like in KDE Discover, for example: https:/
I've attached a naive and trivial patch.
Note: in addition to the patch, you will need to do one of the following to retain the connection between the AppStream data and the desktop file: inkscape. Inkscape. desktop" ) appdata. xml.in: "<launchable type="desktop- id">inkscape. desktop< /launchable> "
- Rename the desktop file to match the AppStream ID (i.e."org.
- Add the following line to inkscape.
Relevant section of the AppStream spec: https:/ /www.freedeskto p.org/software/ appstream/ docs/sect- Metadata- Application. html
[note: not an AppStream expert, take this with a grain of salt, etc]