-
Notifications
You must be signed in to change notification settings - Fork 297
linux: Add metainfo file #1860
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
ReillyBrogan
wants to merge
2
commits into
TwilitRealm:main
Choose a base branch
from
ReillyBrogan:appdata
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
linux: Add metainfo file #1860
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,38 @@ | ||
| <?xml version="1.0" encoding="UTF-8"?> | ||
| <component type="desktop-application"> | ||
| <id>dev.twilitrealm.dusk</id> | ||
| <launchable type="desktop-id">dev.twilitrealm.dusk.desktop</launchable> | ||
| <name>Dusklight</name> | ||
| <summary>Native port of a classic adventure game</summary> | ||
| <developer id="dev.twilitrealm"> | ||
| <name>Twilit Realm</name> | ||
| </developer> | ||
| <url type="homepage">https://twilitrealm.dev</url> | ||
| <url type="bugtracker">https://github.com/TwilitRealm/dusklight/issues</url> | ||
| <metadata_license>CC0-1.0</metadata_license> | ||
| <project_license>CC0-1.0</project_license> | ||
| <content_rating type="oars-1.0"/> | ||
| <supports> | ||
| <control>console</control> | ||
| <control>gamepad</control> | ||
| </supports> | ||
| <description> | ||
| <p> | ||
| Dusklight is a reverse-engineered reimplementation of a classic adventure game. | ||
| It aims to be as accurate as possible to the original while also providing new options, enhancements, and tools to customize your experience. | ||
| </p> | ||
| </description> | ||
|
|
||
| <provides> | ||
| <binary>dusklight</binary> | ||
| <id>dev.twilitrealm.dusk.desktop</id> | ||
| </provides> | ||
|
|
||
| <releases> | ||
| <release version="UNRELEASED" date="2026-12-31"> | ||
| <description> | ||
| <p>Initial Flatpak release.</p> | ||
| </description> | ||
| </release> | ||
| </releases> | ||
| </component> | ||
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Curious how this is meant to be kept up to date. Is this file supposed to be generated or something?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Its usually maintained by hand or generated through the build system or similar.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm avoiding looking too much into it right now but yeah it can either be maintained by hand or automatically generated. That generation could be scripting converting the Github release notes as a post-release step of some kind or using some kind of in-repo changelog (https://blog.tenstral.net/2020/03/maintain-release-info-easily-in-metainfo-files.html). You could also just delete the releases tag from the metainfo and live with the fact that software stores won't show any release notes which is a surprisingly common approach.
I am tracking figuring that out as "Automate release notes generation" in the Flatpak tracking issue.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just have the releases tag in there as a placeholder. If it's decided not to do release notes yet we'll just remove it before submitting to flathub (we can always add it later).