Respect XDG Basedirectories #343
Labels
No Label
abra
abra-gandi
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
democracy
design
documentation
duplicate
enhancement
finance
funding
good first issue
help wanted
installer
kadabra
performance
proposal
question
recipes.coopcloud.tech
security
test
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#343
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I don't want my home-directory littered, not even with symlinks, please respect XDG like any good Linux citizen: https://wiki.archlinux.org/title/XDG_Base_Directory
https://docs.coopcloud.tech/operators/handbook/#understanding-abra
You could either put everything under
XDG_STATE_HOME/abra
or separate theservers
subdirectory intoXDG_DATA_HOME
and potentially some of the other stuff into cache, that way you won't have to tell people to handle subdirectories differently.You can always fall back to an existing
.abra
dir and/or only respect XDG when the respective variables are set.Respect XDG specto Respect XDG BasedirectoriesI've never even heard of
XDG_STATE_HOME
tbh.I don't think splitting up the recipes/servers/etc. into random "cache" dirs would help hacking workflows... especially since folks are used to the directory layout already...
I would'nt be against accepting a change set for respecting the base dirs if it is backwards compatible (no existing installs have to migrate). Hopefully everything under
~/.abra/...
could stay there...(edit: would 👉 wouldn't )
XDG_STATE_HOME has been added in the last revision to fill a gap in the previous directories.
And no, they are not random, my cache dir has plenty of folders which makes backing up and cleaning my device very convenient. Please, I have had discussions about this plenty of times, can't we just respect established standards?
Hu? With backwards compatibility all of this would be no issue.
Workaround for the time being:
export ABRA_DIR=...
(only available on latest HEAD)