Alberto Garcia

Regardless of the tools that we may use to automate the work, I can help with the next releases if you want. Like that I can also have a better overview of what actually needs to be done.

That should be easy to do, the appstream file only needs the changelog entries. What's your usual workflow when you make releases? Because the actual ChangeLog file is very verbose and you need to select what things to highlight for the release notes.

Thanks! Remember that from now on we should add the release notes to the data/net.sourceforge.fuse_emulator.Fuse.metainfo.xml file, see the <release date="2026-03-24" version="1.7.0"> tag for an example. The list of items in the description are the ones that will appear in places like Flathub and such.

Thanks! Remember that from now on we should add the release notes to the data/net.sourceforge.fuse_emulator.Fuse.metainfo.xml file, see the <release date="2026-03-24" version="1.7.0"> tag for an example. The list of items in the ChangeLog are the ones that will appear in places like Flathub and such.

https://sourceforge.net/p/fuse-emulator/fuse/merge-requests/35/

Add AppStream metainfo file

The question is not about reading, but about writing :) Reading $XDG_CONFIG_HOME and then falling back to $HOME/.fuserc is easy and I think that we should probably do it in any case. But when the user wants to save the configuration, do we always write to $XDG_CONFIG_HOME? One possibility is that we move the configuration file from $HOME/.fuserc to $XDG_CONFIG_HOME, so the former silently disappears. Or we can also leave the original in place, but then we'd have two copies and only one would be actually...

I just rebased the patch and created a fork: https://sourceforge.net/u/bertogg/fuse-emulator/ci/bug-510-appstream-metadata/tree/