Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use XDG_CACHE_HOME by default. #22

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Use XDG_CACHE_HOME by default. #22

wants to merge 1 commit into from

Conversation

ghost
Copy link

@ghost ghost commented Dec 14, 2016

As you use '~/.config/vis' directory for vis, what about following XDG for location of FIFO? This is just a proposition.

We can set ABDUCO_SOCKET_DIR or edit config.h anyway.

What other programs do: http://wiki.archlinux.org/index.php/XDG_Base_Directory_support

@martanne
Copy link
Owner

I don't think $XDG_CACHE_HOME is appropriate because we are not dealing with "non-essential data files".

Regarding $XDG_RUNTIME_DIR, the XDG specification defines its lifetime in terms of logins/logouts. The abduco socket obviously has to survive that, otherwise it isn't possible to resume a session. Hence, it also does not seem useful for our case.

Unless I'm misunderstanding how they define login/logout?

@ilyagr
Copy link

ilyagr commented Dec 24, 2024

Perhaps XDG_STATE_HOME is a better place for it according to XDG. At least, https://specifications.freedesktop.org/basedir-spec/latest/#variables and https://wiki.archlinux.org/title/XDG_Base_Directory make it seem like a reasonable place. Abduco session seems close enough to data that needs to "survive application restart" (especially if you consider a detach/reattach cycle as a "restart" of a "client").

Though, looking at this PR, it would be a bit strange to use an XGD_STATE_HOME (or XDG_CACHE_HOME, as currently implemented) environment variable, but not to use the default value for it suggested in https://specifications.freedesktop.org/basedir-spec/latest/#variable .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants