Eric Huss

@Muscraft Here is a test demonstrating it: ```rust #[cargo_test] fn invalid_name_in_git_repo() { // Checks to ignore invalid package name in git repository. let git_project = git::new("bar", |p| { p.file("Cargo.toml", &basic_manifest("bar",...

> Cargo would no longer have a canonical place for the feature. I think what we have for now seems fine.

@Urgau This is still marked as a draft. Is it ready to go?

Why does the bootstrap bump matter?

> But now that I'm writing this comment, I wonder if we're even using the latest version of Cargo in rust-lang/rust? 🤔 No, rust-lang/rust just uses the beta cargo for...

Indeed orphans can be a problem, but usually only when the `rev` is not specified. That does not appear to be the case here. One thing to investigate is that...

> @ehuss Would it be the case that `git gc` removed unreachable objects? Not directly, I don't think. The actions linked above seem to have some caching, but not of...

OK, I think I see one possibility of what is happening. When fetching a repo, cargo doesn't know if a `rev` refers to a commit or a tag. It can...

I'm not quite clear, why does this need a new flag? Why can't it just use separate directories when there is a conflict?

Thanks for the report! As @epage mentioned, I believe cargo looks at PATH to determine the priority, so you can put `~/.cargo/bin` later in the PATH. Closing as a duplicate...