Add FreeDesktop metadata for Linux: vector icon, .desktop launcher file and metainfo.xml for package managers#76
Merged
Conversation
…file and `metainfo.xml`
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
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.
Sorry I've gone quiet for a while there! These files are usually requested by Flathub to be maintained upstream rather than in the flathub-side repository, and would also be useful for any Linux distributors looking to build OpenSupaplex packages for their distro.
The
desktoplauncher file and icon can be copied to specific locations on the user's host system to add an entry for OS to their application menu, while themetainfo.xmlcontains metadata that can be displayed by package managers; this is also what Flathub generate their web listings for apps from.The only ongoing maintenance needed here would be when tagging a new release, a new
<release>element will want adding to themetainfo.xmlwith the version number and release date, and a<url>sub-element pointing to the GitHub release page. Ideally this should be updated before the release is tagged, so the updated release information is included in the tagged release that's being built from.