You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the flatpak package of the Helix uses a basic .appdata.xml file written by the packager (me). Ideally that file should be provided by the app itself. Not only that is the best practice for flathub, that will mean that other packages will be able to use it as well. For example if it will be added to archlinux-appstream-data then software stores on arch linux would be able to recognize it.
Currently on archlinux in gnome-software if you search for "Helix" two things will come up:
One is the version from arch repositories that gets all the info from .desktop file:
And the other from flathub with the .appdata.xml that I wrote:
If all packages would all use .appdata.xml file, software stores could understand that it is the same package. Also current page for native version of the package doesn't have much. No screenshots, not much description, and no licensing information (gnome software marks it as proprietary for that reason). Providing the appstream manifest would also allow you to add more stuff like release notes. (now when I'm looking at it this manifest is really minimal, I could easily add more links, keywords, categories, the video)
We can start by just copying the manifest I wrote into ./contrib/Helix.appdata.xml and put Helix.desktop instead of the flatpak-specific com.helix_editor.Helix.desktop. Also probably replace the license for the metadata file with the one used for this repo.
The text was updated successfully, but these errors were encountered:
Currently the flatpak package of the Helix uses a basic
.appdata.xml
file written by the packager (me). Ideally that file should be provided by the app itself. Not only that is the best practice for flathub, that will mean that other packages will be able to use it as well. For example if it will be added toarchlinux-appstream-data
then software stores on arch linux would be able to recognize it.Currently on archlinux in
gnome-software
if you search for "Helix" two things will come up:One is the version from arch repositories that gets all the info from
.desktop
file:And the other from flathub with the
.appdata.xml
that I wrote:If all packages would all use
.appdata.xml
file, software stores could understand that it is the same package. Also current page for native version of the package doesn't have much. No screenshots, not much description, and no licensing information (gnome software marks it as proprietary for that reason). Providing the appstream manifest would also allow you to add more stuff like release notes. (now when I'm looking at it this manifest is really minimal, I could easily add more links, keywords, categories, the video)We can start by just copying the manifest I wrote into
./contrib/Helix.appdata.xml
and putHelix.desktop
instead of the flatpak-specificcom.helix_editor.Helix.desktop
. Also probably replace the license for the metadata file with the one used for this repo.The text was updated successfully, but these errors were encountered: