Ugh, the maintainer of the Debian bcachefs-tools package just orphaned it because its Rust dependencies are moving too fast. jonathancarter.org/2024/08/29/…
So, I need to be careful not to cause that same problem in AccessKit, especially if my current (draft) merge request to use AccessKit in GTK 4 (via the C API) is finished and accepted.
karolherbst 🐧 🦀
in reply to Matt Campbell • • •iooioio
in reply to Matt Campbell • • •Guido Günther
in reply to Matt Campbell • • •Tobias Hunger
in reply to Matt Campbell • • •my impression is that it is more that the rust dependency handling is incompatible with how Debian wants to handle dependencies. Note that this is true for go, JS, ... just as well.
In the bcachefs case they built against *newer* dependencies than those the tool had set in their Cargo.toml.
I doubt you need to worry with accesskit: Debian will pick a version and never update that again anyway.
Matt Campbell
in reply to Tobias Hunger • • •Tobias Hunger
in reply to Matt Campbell • • •Keep the MSRV low, that is about as much as you can do. At least the rustc the distros pick might still work then.
Distribution will force whichever version of dependencies they picked anyway... whether or not that causes the whole thing to crash or not.
I started to use `cargo install --locked` to make sure to get the binaries the devs tested and not some random crap mutilated by some distribution packager with no clue about rust or programming.
lonjil
in reply to Matt Campbell • • •Matt Campbell
in reply to lonjil • • •