Error: No viable remote package found fallback wanted: cargo install

[r3h0]

TL;DR, binstall fails when quickinstall release is missing or when other errors occur. Instead of failing, I'd like a fallback option that tries cargo install before giving up.

Overall this project is really promising! I have a dozen or so changes like this that I want to make to my Dockerfile:

-wget -q https://github.com/watchexec/watchexec/releases/download/cli-v1.18.6/watchexec-1.18.6-x86_64-unknown-linux-musl.tar.xz -O - | tar xJ watchexec-1.18.6-x86_64-unknown-linux-musl/watchexec --strip-components=1
+cargo binstall --no-confirm watchexec --version 1.18.6

However, I've found that several of my packages neither have binstall metadata nor are they cached on https://github.com/alsuren/cargo-quickinstall/releases.

cargo binstall --no-confirm watchexec                 
14:57:13 [INFO] Installing package: 'watchexec'
14:57:13 [INFO] Checking for package at: 'https://github.com/watchexec/watchexec/releases/download/v1.17.1/watchexec-x86_64-unknown-linux-gnu-v1.17.1.tgz'
14:57:14 [INFO] Sending installation report to quickinstall (anonymous)
14:57:15 [INFO] Checking for package at: 'https://github.com/alsuren/cargo-quickinstall/releases/download/watchexec-1.17.1-x86_64-unknown-linux-gnu/watchexec-1.17.1-x86_64-unknown-linux-gnu.tar.gz'
14:57:16 [ERROR] File does not exist remotely, cannot proceed
Error: No viable remote package found

For context, here's the cargo-quickinstall docs:

If we don't have a pre-compiled version, it will fallback to cargo install automatically.

Does binstall intentionally lack that behavior? If so, it might be nice to have a note about that on the README; I expected a fallback, considering this project's relationship to quickinstall. If not, consider this a feature request.

[passcod]

Yes, it's planned. But good to have an issue just for it!