[x] I searched the issue tracker for other issues covering my case
[x] This is a Launcher issue. (Usually if you can reproduce it with a fresh instance)
Describe the bug
On Linux, GDLauncher currently uses the folder ~/.config/gdlauncher-next in order to store all application related data, ie. instance files. This is in violation of XDG Base Directory spec, which dictates that the .config folder is for configuration files only, and that program-related data should go in ~/.local/share.
To Reproduce
Steps to reproduce the behavior:
Use Linux
Run the GDLauncher app image
Download an instance (any)
Right click the instance, and open the folder. It is in ~/.config.
Expected behavior
I expected it to use ~/.local/share. Dumping program data into .config is generally considered by Linux users to be a program misbehavior.
Possible solutions
Use ~/.local/share, or get the desired path from the XDG_DATA_HOME environment variable, as is dictated by XDG Base Directory specification.
Describe the bug On Linux, GDLauncher currently uses the folder ~/.config/gdlauncher-next in order to store all application related data, ie. instance files. This is in violation of XDG Base Directory spec, which dictates that the .config folder is for configuration files only, and that program-related data should go in ~/.local/share.
To Reproduce Steps to reproduce the behavior:
Expected behavior I expected it to use ~/.local/share. Dumping program data into .config is generally considered by Linux users to be a program misbehavior.
Possible solutions Use ~/.local/share, or get the desired path from the XDG_DATA_HOME environment variable, as is dictated by XDG Base Directory specification.
Screenshots N/A
Operating System:
Additional context
N/A