5 ms·
For those missing the context; this guy wants new Rust software on Debian stable’s old Rust toolchain. And complains about it in every Rust thread on HN. A sim
by loeg 4y ago
For those missing the context; this guy wants new Rust software on Debian stable’s old Rust toolchain. And complains about it in every Rust thread on HN.
A similar problem afflicts other software in Debian stable; Rust is not unique. The reasonable solution is to stop using Debian stable if you want updates.
- malkia 4y agoor find ways to override and install latest, for example latest LLVM that would work on debian stable - https://apt.llvm.org/ https://apt.llvm.org/ (maybe similar for rust?). I've switched to this on my debian stable so that I can compile carbonlang (it needs llvm12, debian stable had only llvm11) - with above I've actually got llvm15, and then week ago switched to llvm16 (I can adjust that back to say llvm14 if I want).
- baby 4y agoWait can't you just use rustup?
- krastanov 4y ago`rustup` is awesome for me as a developer. It is not convenient if I am a sysadmin that wants everything to be stable and consistent: I can not afford to use special version/package manager for every single language. It is fair to complain that rust (or python, or julia, or any other language with built-in environment/package/version manager) do not play nice with OS package managers. OS package managers are starting to take "vendoring" a bit more seriously because of this.
- rascul 4y agoThe OS package managers seem to be figuring it out, though. I've noticed that both opensuse and debian have a number of rust programs in their repos.
- pornel 4y agoDebian does it the hard way, by making a Debian package for every crates-io dependency used and patching Rust programs to use Debian's forked deps instead. It's seems like a massive pain for them, and has zero value for Rust end users, since normal Cargo won't use any of this. Rust often carries its own bugfixes to its LLVM version (before they're accepted upstream). Debian unbundles LLVM from Rust and makes Rust use Debian's LLVM, which creates a risk of undoing Rust's bugfixes and causing miscompilations. I don't think anyone should be using Debian-packaged Rust. Debian's and Rust's policies are fundamentally incompatible. This results in Debian having a hopelessly outdated inferior package that is a pain for both Debian users and the rest of the Rust ecosystem.
- superkuh 4y agoWe're both talking about the same elephant but we're obviously touching different ends of it. The end I'm touching smells really bad. The fact that so many distros have to go extremely far out of their way, breaking their standard processes, shows that Rust is unique in it's tomfoolery. You guys are advocating for the tail to wag the dog.
- troutwine 4y agoAt the most recent RustConf William Brown spoke about how OpenSUSE deals with Rust[1]. If I remember correctly from his talk they started doing something very similar to Debian and then eventually settled on "just use rustup". I wish I had taken better notes because there was more nuance to the history there but I think they'll release the videos of the talks soon. [1]: https://rustconf.com/schedule#how-we-ship-rust-in-opensuse https://rustconf.com/schedule#how-we-ship-rust-in-opensuse
- baby 4y ago
- pavon 4y agoTo clarify, without weighing in on the merits of his complaint, what he is saying is that he wants to use Debian Stable's toolchain and is complaining that the ecosystem (crates on cargo.io) move to use the latest features so quickly, and don't have stable backport releases, which makes this difficult to do. Edit: Reworded to remove disagreement.
- Macha 4y agoI'm not saying now that's opposed. If you want Debian to curate your compiler version, then use the Debian curated versions of your Rust software for compatibility.
- loeg 4y agoI think you're agreeing with me, but framing it as disagreement. > the ecosystem (crates on cargo.io) move to use the latest features so quickly They use the new features in new software -- implying he wants to use that new software. If he uses the old versions that predate the new features, this wouldn't be a problem for him.
- pavon 4y agoYes, I did misread your post, sorry. Reworded mine to be a clarification rather than a contradiction.
- superkuh 4y agoThe Debian example you're referring to was back from the release of 11. It's rustc was only 3 months old and already couldn't compile. That's not a "Debian is old" problem and it was only one instance. I've run into the same problem on other OSes as well. No OS hosted repo can keep up with rust and it's particular selection of bleeding edge types. And it's hardly every Rust thread. There are far too many rust threads to even count, let alone comment on.
- pas 4y ago> No OS hosted repo can keep up with rust and it's particular selection of bleeding edge types. what? why? someone has to click the approve on the update+build+publish pipeline.. and that's in most repos anyway.
- msbarnett 4y ago> No OS hosted repo can keep up with rust and it's particular selection of bleeding edge types. Seems empirically false https://archlinux.org/packages/extra/x86_64/rust/ https://archlinux.org/packages/extra/x86_64/rust/ If your distro is unwilling to update a package with a single backwards-compatible minor version bump every 6 weeks, that’s a cultural issue, not a technical one. The “stability“ Debian imagines it gets from shipping a years-old compiler version instead of keeping up-to-date with non-breaking compiler updates is entirely mythical. Pick a less sclerotic distro next time.
- superkuh 4y agoOh, okay, we'll just write off the entire concept of release based distributions because of one start-up programming language then? Everyone switches to rolling release? That's pretty absurd.
- fweimer 4y agoDebian packages rustc-mozilla for building Firefox. Firefox ESR 102 will need Rust 1.59.0, and that version has already been uploaded to stable-proposed-updates. 1.59 is not that old (it's from February 2022), and this actually builds after installing rustc-mozilla (with cargo even): use std::arch::asm; fn main() { unsafe { asm!( "syscall", in("eax") 60, in("edi") 0, out("rcx") _, out("r11") _, } } I guess for the same reason, there's now an LLVM and Clang 13 build in Debian stable, too. I'm not entirely happy how Mozilla forced Debian's hand here. But it means that there is a relatively current, Debian-blessed Rust compiler, and you can use it for your own builds if you are willing to upgrade from time to time.
- xvilka 4y agoIt's a problem for any fast moving software, not only Rust. Debian (and Ubuntu which is based on it) is notoriously slow on updating many packages.