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

zef should store cached repositories in XDG_CACHE_HOME on Linux #158

Open
samcv opened this issue May 4, 2017 · 4 comments
Open

zef should store cached repositories in XDG_CACHE_HOME on Linux #158

samcv opened this issue May 4, 2017 · 4 comments

Comments

@samcv
Copy link
Contributor

samcv commented May 4, 2017

On Linux the proper folder to put the cached repositories is ~/.cache, or XDG_CACHE_HOME if it defined and non-empty.

Config files should be stored in ~/.config or XDG_CONFIG_HOME if defined and non-empty.

~/.cache/zef or ~/.config/zef would be neater and allow us to separate the cache files from the configuration files as well as fitting with the XDG

Thoughts on this?

@ugexe
Copy link
Owner

ugexe commented May 4, 2017

Yes, zef should follow all the items in https://specifications.freedesktop.org/basedir-spec/basedir-spec-0.6.html

...but shouldn't rakudo do this as well?

@samcv
Copy link
Contributor Author

samcv commented Jun 19, 2017

@ugexe what is the difference between ~/.zef/tmp and ~/.zef/store ?

It would seem .zef/tmp would likely go in ~/.cache/zef but is the store folder also cache information or is it not?

@ugexe
Copy link
Owner

ugexe commented Jun 19, 2017

They are essentially the same thing. tmp/ is where things get fetched to initially, and then they get extracted/checked-out to store/. So tmp/ is meant to be something that can be nuked whenever, and store/ is essentially a CompUnit::Repository so nuking it will affect other things (in this case just if zef can fetch from the cache or not).

@ugexe
Copy link
Owner

ugexe commented Jun 23, 2017

#179

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

No branches or pull requests

2 participants