Open ASHGOLDOFFICIAL opened 5 months ago
I see it as a compile switch/define: A user starts either the current way or uses XDG. I don't like the idea to have it as configuration switch. There might be migration scripts to move exiting config files et.al. from one location to the other and vice-versa.
@ASHGOLDOFFICIAL , @retrobit, @gbiggs it is merged into main/HEAD . Please do also test on your side and report any issues here. Documentation: https://gemba.github.io/skyscraper/XDG/
Benefits Specification is widely adopted. It allows to clean home directory by moving configs/cache/etc to specified locations. Another benefit is separation of configuration files, cache and data files. By moving
./cache/
folder and other files/folders that are not supposed to be modified by user to another location, you can ensure they will not be modified by user../cache/
XDG_CACHE_HOME
orXDG_DATA_HOME
./resources/
XDG_DATA_HOME
./config.ini
,./artwork.xml
and examplesXDG_CONFIG_HOME
./reports
,skipped-*
XDG_STATE_HOME
./import/
and other filesXDG_DATA_HOME
To remain backwards compatible, add config option like
xdg
. When this option is enabled, and XDG* variables are set, they will be used. If XDG* variables aren't set either fallback to~/.config/
,~/.local/state
or~/.cache
(preferred) or use current~/.skyscraper
.Useful resources