bug#62064: Why is only rust-1.60 exported when 1.65 is defined?

["Jonas Møller via Bug reports for GNU Guix" <bug-guix@gnu.org>]

[-- Attachment #1: Type: text/plain, Size: 1108 bytes --]

> Well, the issue when exporting ’rust-1.65’ is that it would possible
> incompatible with the Rust packages provided by Guix and compiled with
> ’rust’ (1.60).

Rust has very strong stability guarantees between 1.x releases, and has a very extensive set of tooling/infrastructure to make sure no breaking changes make their way into a release (see crater [1]). Any Rust-based package big enough to be packaged by Guix will have had its test-suite confirmed to work with the new release of cargo/rustc long before any new release is made (and in many cases before pull-requests are merged.)

Nevertheless, rebuilding all Rust packages on every rustc release isn't strictly necessary. (Improvements in optimizations do happen, but they are mosty minor release-to-release.)

But I agree with your ’package-with-explicit-rust’ idea, it is very unfortunate that "Rust, the development environment used by Guix users building Rust software" and "Rust, the build environment we use to build all Guix Rust packages" got conflated in Guix.

[1]: https://github.com/rust-lang/crater

— Mvh Jonas Møller

[-- Attachment #2: Type: text/html, Size: 2087 bytes --]