On 1/17/19 5:58 AM, Manish Goregaokar wrote:
In clippy's case the version number is vestigial, any changes
will be purely cosmetic (we'll likely 1.0 it and leave it at that)
I figured as much. If you're not planning to match versions with rustc,
then at least 1.0 seems nicer. However, I see it's also still getting
occasionally published on crates.io, currently 0.0.302, so maybe API
semver concerns apply. I guess you could kludge "--version" separate
from the crate version, like cargo does itself.
Clippy is meant to be built along with the compiler using the
submodule'd version, so switching versions for a given compiler isn't
something we support anyway.
Right -- we do build it this way from the rustc-src tarball, and the
resulting subpackage is tied to the exact NVR of the compiler to match
libraries, e.g. "Requires: rust(x86-64) = 1.31.1-9.fc30".