CARGO_HOME is not used when storing advisory-db in 0.14.23
Nukesor opened this issue · comments
Arne Christian Beer commented
Describe the bug
Despite $CARGO_HOME
being set, cargo-deny
writes into ~/.cargo
.
This is a regression, as this was fixed back in 0.8.2. See #302
To reproduce
rm -r ~/.cargo/advisory-db
export CARGO_HOME=~/.local/share/cargo
cd one/of/your/projects
cargo deny
cargo-deny version
cargo-deny 0.14.23
What OS were you running cargo-deny on?
Linux
Additional context
No response
Arne Christian Beer commented
Nevermind. Seems to be some environment shenannigans on my end.