conda-forge/conda-forge.github.io

Document `cargo install --locked --no-track`

Opened this issue · 3 comments

wolfv commented

Where should the content be added?

In the knowledge base or even as a linter

What should be added?

We should (force) people to use cargo install --locked --no-track. The --no-track option prevents cargo from writing $PREFIX/.crates2.json and $PREFIX/.crates.toml files.

If that option is not used, all Rust packages clobber each other.

Additional information

No response

xhochy commented

We could probably make a linter out of this.

  • 🎉1
jaimergp commented

Is there an env var cargo accepts for this? Maybe the rust compiler package could auto set it if used within conda-build?

mbhall88 commented

Is there an env var cargo accepts for this? Maybe the rust compiler package could auto set it if used within conda-build?

Doesn't appear to be https://doc.rust-lang.org/cargo/reference/environment-variables.html, though $CARGO_INSTALL_ROOT could be a useful one for us to auto set?