-
-
Notifications
You must be signed in to change notification settings - Fork 8
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
Consider moving CAS to platform-standard cache directories #47
Comments
This should definitely be done. IIUC this crate is the thing to use: https://crates.io/crates/dirs @kamalmarhubi do you want to take a crack at this? |
To be clear, |
As to #9, the CAS definitely can always be blown away in normal use. The self-modifying idea is aimed at system installers; i.e.: |
This is now released in 0.4.0: https://github.com/a-scie/jump/releases/tag/v0.4.0 |
Ran across this project via pantsbuild.slack.com lurking.
Small suggestion: instead of
~/.nce
, store the CAS in$XDG_CACHE_HOME/{scie,nce,whatever}
on systems that follow XDG, and in~/Library/Caches/{scie,nce,whatever}
on macos—and probably somewhere under%localappdata%
on Windows; less sure about that one.This makes it clear it's fine to blow away (eg, to free up space), and also removes some clutter from
$HOME
. It's probably easier to change this before widespread use of scie-packaged programs. :-)Edit: I just saw #9 which probably conflicts with the idea that the CAS can be blown away. In that case, the equivalent of
$XDG_DATA_HOME
might be better?The text was updated successfully, but these errors were encountered: