Hi Paul And Maxime, > Even if you didn't succeed at updating _all_ dependencies, if you > have patches for some of them, please send them. It will help people > in the future with updating rust-analyzer or other rust packages.
I had a patchset (here: https://issues.guix.gnu.org/46162) adding rust-analyzer and the rest of the other tools that come part of the rust tree. I think it would not be too much work to add if added as outputs/companion packages to rust itself. > For many people, a vaguely recent-ish version would be sufficient. At > least, that's the case for C, GCC and Clang. > ... > It might be possible to do "cargo xtask install --server", but many > advantages of Guix would be lost. That worked for me. I was using guix' rust tooling for my job. I much prefer using guix over rustup/cargo. I just had to patch rust a lot and my patches haven't made it in (yet?). > Indeed, e.g. it would be nice to figure out how to eliminate #:skip- > build?, replace #:cargo-inputs by regular inputs, figure out how to > stop having to package multiple versions of the same package. My gut feeling is still that the functional package managers need to collaborate with the rust/cargo team. Rust itself just does not lend itself well to the model. It is a shame since we share many of the same goals (reproducibility and reliability come to the top of mind). Kindly, John
