Can’t exactly support a platform named tankie.tube.
Can’t exactly support a platform named tankie.tube.
This article has big “she’s not good enough, so we should stay home” energy.
The headline seems like a particularly reductive and shitty take, especially considering she’s a child of Indian and Jamaican parents.
Dev being an asshole and not accept Linus’ code review = Rust is bad?
But, as the debian dude has learned… Rust programs will 99.999 % work if they can be compiled.
That’s a dumb statement. Every tool needs unit tests. All of them!
If grep complied, but always returned nothing for every file and filter, then it’s still not “working”. But, hey, it compiled!
The OP is about packaging issues with userspace utilities due to version pinning in Rust
No, it’s about Bcachefs specifically. It’s literally in the title. Discussions around Rust version pinning are a useful side conversation, but that’s not what the OP is about.
So if your Rust app is built against up to date libraries in Cargo, it’s going to be difficult to package those apps in Debian when they ship stable, out of date libraries since Debian’s policies don’t like the idea of using outside dependencies from Cargo.
As they should. You don’t just auto-update every package to bleeding edge in a stable OS, and security goes out the window when you’re trusting a third-party’s third-party to monitor for dependency chain attacks (which they aren’t). This is how we get Crowdstrike global outages and Node.JS bitcoin miner injections.
If some Rust tool is a critical part of the toolchain, they better be testing this shit against a wide array of dependency versions, and plan for a much older baseline. If not, then they don’t get to play ball with the big Linux distros.
Debian is 100% in the right here, and I hope they continue hammering their standards into people.
You’re posting on hexbear.net…