Please consider updating the crate on crates.io

[andreacorbellini]

I've been using cross for my projects by installing it via cargo install --locked cross. This has worked fine for me until I hit a linking issue on sparc64-unknown-linux-gnu upon updating a dependency.

This issue was caused by my local version of cross (from crates.io) shipping Glibc 2.23, and I was confused because the latest README on GitHub was listing Glibc 2.31. I later realized that cross on crates.io has not been updated in over 2 years.

The only way to get a recent version of cross is to install it directly from the Git repository (via cargo install cross --git https://github.com/cross-rs/cross or similar), which, to be fair, is documented on the README.

However I would like to point out that nowhere it says that the version on crates.io is stale and should not be used. Could you please do one or more of the following:

1. Update the version on crates.io
2. Add a warning to the README that says that the version on crates.io is stale
3. Publish a dummy release on crates.io that warns users that it should not be used

Thanks.

[andreacorbellini]

I would also like to add that the git repository doesn't have tags past v0.2.5, which makes it hard to include a cargo install command in a CI script in a way that prevents backwards-incompatible changes to slip in.

[Emilgardis]

Please see #1290

There's work needed to be done before a release can be made. But yes, it should be done. It's not reasonable imo to do a "trick" release, I'd rather make it a proper release.

[Emilgardis]

I would also like to add that the git repository doesn't have tags past v0.2.5, which makes it hard to include a cargo install command in a CI script in a way that prevents backwards-incompatible changes to slip in.

You can install from a git repo with a specific commit to checkout

cargo install cross --git https://github.com/cross-rs/cross --rev 36c0d78