Alberto Garcia

But how would you do that? That function only returns the directory, it doesn't even know what the config file name is, and it also doesn't know if the caller wants to read the config file or to write it. If you want to avoid defining compat_get_fallback_config_path() for other architectures without changing significantly the logic, we can add an option like --use-xdg-config to configure.ac and then something like this in the code: if( !compat_file_exists( path ) ) { #ifdef XDG_CONFIG_HOME /* Look...

Here's the merge request: https://sourceforge.net/p/fuse-emulator/fuse/merge-requests/38/

Store the configuration file in the XDG configuration directory

Store the configuration file in the XDG configuration directory

Store the configuration file in the XDG configuration directory

What's the plan with all the SDL versions? Are we going to support all three? I think that with the existing compatibility layers, and given that SDL3 is relatively recent, we can stick to SDL2 for a little. Also, SDL2 is more than ten years old so if the SDL2 support in Fuse is as good as the SDL1 one I would drop the latter, like we did with GTK2. But we shouldn't do it until we're certain that there are no important regressions.

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.