If you actually try building the one on crates.io, it won't build, the
0.300 series of versions (and the tail end of 0.200) all deliberately fail
to compile and throw an error message.
The crates.io copy purely exists to redirect people to using rustup, since
clippy *used* to be updated with cargo install.
Thanks,
-Manish Goregaokar
On Thu, Jan 17, 2019 at 1:00 PM Josh Stone <jistone(a)redhat.com> wrote:
On 1/17/19 5:58 AM, Manish Goregaokar wrote:
> In clippy's case the version number is vestigial, any changes there
> 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".