linux: Add metainfo file#1860
Conversation
Split from TwilitRealm#1191 and adjusted for the correct appId and to remove any trademarks. Credit to @Gabantax Signed-off-by: Reilly Brogan <reilly@reillybrogan.com>
| </provides> | ||
|
|
||
| <releases> | ||
| <release version="UNRELEASED" date="2026-12-31"> |
There was a problem hiding this comment.
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.
Its usually maintained by hand or generated through the build system or similar.
There was a problem hiding this comment.
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.
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).
Signed-off-by: Reilly Brogan <reilly@reillybrogan.com>
3 participants
Split from #1191 and adjusted for the correct appId and to remove any trademarks.
Note: I don't really want to get bogged down in the weeds of getting this perfect as part of this PR. I just want this in place so I can use it in future PRs. Someone who really cares about the presentation of Dusklight can take up the task of improving it after.
Credit to @Gabantax