Put GameHub config files in /home/.config/

[ghost]

Heya.
I was trying to understand how GameHub was working since I met some random entry-deleting issues, and I just realized the real culprit of this was not a failure in the source code, but Stacer just doing what I said it to do : cleaning caches.

The thing is you apparently put GameHub config files in the /home/.cache folder, and don't take any offense but it's not very clever since any cleaning software would, by default, wipe this location of its content.

I thing it would be better to put these config files in .config by default, so that people are not disturbed to see their custom entries for unknown reasons.

[tkashkin]

Maybe you're right. I should move games database to $XDG_CONFIG_HOME.

I think it would be better to do it some time in the future since refactoring branch will likely have other breaking changes. It would also be a good opportunity to restructure database without keeping compatibility with existing databases.

It's implemented this way since beginning when it made a bit more sense. Games database was initially more like a cache, especially when GameHub didn't support custom games.

Other things like graphics cache and other caches should probably still remain in $XDG_CACHE_HOME.

[ghost]

Ok, I'm happy you noticed my report about it. :)

[prettyv]

I believe it would be better to put the database in $XDG_DATA_HOME once you get to it. E.g. lutris also puts its database there and it makes more intuitive sense to me since it's not strictly configuration data that is stored there.

[tkashkin]

I've created a discussion for changes for the next major release, you can add your suggestions there.