`cargo --version --verbose` should give more information (and perhaps have an alias like "bugreport")

[joshtriplett]

Things to include:

• rustc version
• OS and OS version (host system). (This includes detecting Linux distribution if possible; some bits of /etc/os-release would suffice for a start.)
• Default target
• git hash of the crates.io index. (This would work well with future cargo options to pretend the index was at that point, to help reproduce issues.)

[ehuss]

cc #6275

[epage]

#9968 gets us most of what is asked for.

I wonder if we should update our template to include this.

Now for a "bugreport", I see that as separate as we'd want to evaluate including

• config
• maybe some aspects of the project

It wouldn't be important to include everything up front but to have an idea of what we might want to include and make sure its possible.

[weihanglo]

The other things left is rustc and crates.io index, which is a bit odd and tricky to add.

• Rustc version is affected by several configs and environment variables, such like RUSTC and other wrappers.
• crates.io index, like rustc version, is a dynamic value fitting in the same category.

They are not static so perhaps cargo config get or something lese is a better way for displaying the values.

[epage]

We do dynamically write out the version, so being dynamic in cargo version --verbose or a cargo --bugreport is probably fine. While we might have other commands, like cargo config, to query things, the idea would be that we capture everything relevant for a bug report.

[weihanglo]

Sorry for the confusion. I meant configurable not dynamic. I don't think libgit2 or curl or ssl is really configurable at this time. That's a difference to me.