Jacob Finkelman

@pietroalbini suggested a command that would clean up files needed to build a dependency but not needed to use that dependency. `cargo clean-everything-except-the-minimum-needed-not-to-rebuild-deps` @joshtriplett suggested that we move those files...

cc some other discussion going on at https://github.com/rust-lang/cargo/issues/5885#issuecomment-445015842

`git-fetch-with-cli = true` is one work around. You may also be interested in https://github.com/rust-lang/cargo/issues/9069 witch removes the use of git from the index.

I find the questions of longer SHAs confusing and a little premature. What is the timeline for git to support them? GitHub? LibGit2? What is the time pressure on Cargo?...

Sorry for the inconvenience! > Ideally whatever service `cargo publish` talks to wouldn't say "yes" until it had done it. Or maybe `cargo publish` could at least have an option...

cc https://github.com/rust-lang/cargo/pull/5183 and https://github.com/rust-lang/rfcs/pull/1615

At the moment I would start by removing the mtime based system and replacing it with a hash based one. (except for the corner cases where we have to use...

I just came across a [long blog post](https://apenwarr.ca/log/20181113) on the troubles with using mtime in build tools. It discusses using only hash, and points out that [go switched to that](https://github.com/golang/go/commit/7dea509703eb5ad66a35628b12a678110fbb1f72),...

If there was progress it would have been linked here. As I recall I thought it could be done strate forwardly, but the fact that Eric's branch did not work...

Thank you for the clear explanation of the blocking issue with this approach! I think there was some work towards a "rustc in the loop" version at https://github.com/rust-lang/cargo/pull/8623, bushing that...