-
Notifications
You must be signed in to change notification settings - Fork 93
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
Replace $HOME/.xargo with $XDG_DATA_HOME/xargo #46
Comments
Cargo uses HOME not XDG_HOME_DIR AFAICT so I'd prefer not to differ from Cargo on this matter. |
Huh? Cargo still uses |
@linkmauve I grepped for xdg in Cargo repository and there's only one match in a test, which actually unsets the env var. My installation also uses ~/.cargo and there's @SShrike confirmation. The "in the process" links you mention point to a RFC which hasn't been accepted. I'd be happy to move Xargo to XDG after Cargo does it but I won't if Cargo doesn't. I'm going to close this because it's not actionable until Cargo makes the change. Feel free to open a new issue by the time Cargo moves to XDG! |
46: Fix warning about implicit trait objects r=phil-opp a=phil-opp Fixes japaric#45 Co-authored-by: Philipp Oppermann <[email protected]>
Cargo supports setting the |
@jakbyte is anything wrong with |
it took me a year to see this, but it does seem to work 🙂 |
In order to respect the XDG Base Directory Specification, like cargo before it, xargo should switch to the standard
$XDG_DATA_HOME/xargo
directory (by default$HOME/.local/share/xargo
when$XDG_DATA_HOME
isn’t set).The text was updated successfully, but these errors were encountered: