mirror of https://github.com/jdx/mise
fix: add clarification on RUSTUP_HOME and CARGO_HOME (#4759)
I was curious about how mise handled CARGO_HOME and RUSTUP_HOME, but was only able to find out by poking in the source. Hopefully this adds some clarification for others.
This commit is contained in:
parent
4a8f094414
commit
178360664a
|
@ -1,9 +1,10 @@
|
||||||
# Rust <Badge type="warning" text="experimental" />
|
# Rust <Badge type="warning" text="experimental" />
|
||||||
|
|
||||||
Rust/cargo can be installed which uses rustup under the hood. mise will install rustup if it is not
|
Rust/cargo can be installed which uses rustup under the hood. mise will install rustup if it is not already
|
||||||
already installed and add the requested targets. By default, mise uses the default location of rustup/cargo
|
installed and add the requested targets. By default, mise respects the `RUSTUP_HOME` and `CARGO_HOME` environment
|
||||||
(`~/.rustup` and `~/.cargo`), but you can change this by setting the `MISE_RUSTUP_HOME` and `MISE_CARGO_HOME`
|
variables for the home directories and falls back to their standard location (`~/.rustup` and `~/.cargo`) if they are
|
||||||
environment variables if you'd like to isolate mise's rustup/cargo from your other rustup/cargo installations.
|
not set. You can change this by setting the `MISE_RUSTUP_HOME` and `MISE_CARGO_HOME` environment variables if you'd like
|
||||||
|
to isolate mise's rustup/cargo from your other rustup/cargo installations.
|
||||||
|
|
||||||
Unlike most tools, these won't exist inside of `~/.local/share/mise/installs` because they are managed by rustup.
|
Unlike most tools, these won't exist inside of `~/.local/share/mise/installs` because they are managed by rustup.
|
||||||
All mise does is set the `RUST_TOOLCHAIN` environment variable to the requested version and rustup will
|
All mise does is set the `RUST_TOOLCHAIN` environment variable to the requested version and rustup will
|
||||||
|
|
Loading…
Reference in New Issue