Arch Linux User Repository

if you're using rustup, you can try to patch in a rust-toolchain file[1] which contains your preferred toolchain(e.g. stable-1.40.0) and rustup will make sure to use it. I just don't know if you can make that a range... A workaround here would be to update that patch accordingly with each version to match the current stable branch or else to just pin it to 1.32.

[1] https://doc.rust-lang.org/nightly/edition-guide/rust-2018/rustup-for-managing-rust-versions.html

Yeah, no problem, I suspected it's something like that. As I say it's not too important because I am using the -bin package for now. Thanks for your efforts anyway!

@Flubbadub Good question. The problem with rustup is that you can't properly specify what Rust version must be used (like what is possible when using rust>=1.32). Because of this, the rust>=1.32 dependency is set, which is not compatible with the rustup package.

I did try to detect the installed Rust version when used through rustup when installing the package, to warn the user if they're using an outdated Rust version. But that didn't work so well. I might give it another try soon. If that works, the rust dependency can be removed, allowing you to use either rust or rustup as cargo provider which solves your issue (if that makes sense).

Is it possible to make this work with rustup? Currently it tries to make me install rust in order to build it even though rustup provides rust. I think this is due to the version of rust being specified - it works if I just remove the version constraint. I did wonder if this was an issue with the AUR helper program I use but I also tried building with makepkg directly and that has the same issue.

For now I am just using ffsend-bin so no worries if this is difficult/not possible. I had a quick look and couldn't find a decent way.