bjorn3

Cargo.{toml,lock} should probably also be read-only.

Every crate version is stored in a separate directory. This is necessary to be able to cache multiple crate versions at once. And because of this we never need to...

> On unix systems it might make more sense for cargo to run as its own user. There is no way to do that as an unprivileged user. And requiring...

The immutable flag on linux can only be set by root as it prevents even root from modifying it.

The umask is process global, but someone may be creating files concurrently with cargo when using cargo as library. Also for directories setting the umask I believe will require using...

> Can't we get their contents as needed, in-memory? Rustc currently doesn't support that. We could add it, but build scripts and proc macros will still need it extracted somewhere...

Sccache doesn't cache source code. It reads the `.d` file emitted by rustc to know when it needs to recompile. If rustc were to compile tarballs, this `.d` file would...

> > It does not enable long paths if the user cannot or will not enable long path awareness in the registry (e.g. OS too old, IT policies, etc). >...

Maybe a first step would be to move everything that needs to be compiled for the host even when cross-compiling to a new `target/.build` directory. As a next step we...

The host triple is included in the `rustc -vV` output, which I think is enough to cause cargo to use different filenames.