You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hmm, I'd have to look at the history, cargo-deny never explicitly supported $CARGO_HOME but it's possible the behavior or crate used to resolve the root cargo path has changed.
Describe the bug
Not really a bug report, just a clarification whether the difference in behaviour between 0.7.3 and 0.8.1 is intentional.
To Reproduce
Steps to reproduce the behavior:
deny.toml
, i.e. defaults are usedcargo deny check
Observed behavior
In 0.7.3:
Databse is downloaded to
$CARGO_HOME/advisory-db
In 0.8.1:
Databse is downloaded to
$HOME/.cargo/advisory-db
, ignoring$CARGO_HOME
.Additional context
In my builds
$HOME
is not RW, only$CARGO_HOME
is so usingcargo-deny
with defaults started failing.The new behaviour is maybe in line with
cargo deny init
setting the db-path as~/.cargo/advisory-db
in both 0.7.3 and 0.8.1.Is this change intentional?
The text was updated successfully, but these errors were encountered: