feat: Install via cargo binstall #583

wetneb · 2025-09-03T09:43:37+02:00

wetneb commented

2025-09-03 09:43:37 +02:00

It provides an easier way to install crates without compiling them
locally.

It provides an easier way to install crates without compiling them locally.

wetneb added 1 commit

2025-09-03 09:43:38 +02:00

feat: Install via cargo binstall

/ test (pull_request) Successful in 44s

Details

c56a1e75f8

It provides an easier way to install crates without compiling them
locally.

ada4a reviewed

2025-09-03 14:59:10 +02:00

Cargo.toml

					
				@ -122,0 +123,4 @@

				[package.metadata.binstall]

				pkg-url = "{ repo }/releases/download/v{ version }/{ name }_{ target }{ archive-suffix }"

				bin-dir = "{ bin }{ binary-ext }"

				pkg-fmt = "tgz"

ada4a commented

2025-09-03 14:52:50 +02:00

I think this won't work, because our links looks like this:

https://codeberg.org/mergiraf/mergiraf/releases/download/v0.14.0/mergiraf_x86_64-unknown-linux-gnu.tar.gz

Whereas, AFAICT from the docs, pkg-fmt = "tgz" sets archive-extension to .tgz.

But if I try to do that for the link above:

https://codeberg.org/mergiraf/mergiraf/releases/download/v0.14.0/mergiraf_x86_64-unknown-linux-gnu.tgz

I get a 404.

We should probably specify archive-suffix = ".tar.gz" explicitly

I think this won't work, because our links looks like this: > https://codeberg.org/mergiraf/mergiraf/releases/download/v0.14.0/mergiraf_x86_64-unknown-linux-gnu.tar.gz Whereas, AFAICT from [the docs](https://github.com/cargo-bins/cargo-binstall/blob/main/SUPPORT.md#support-for-cargo-binstall), `pkg-fmt = "tgz"` sets `archive-extension` to `.tgz`. But if I try to do that for the link above: > https://codeberg.org/mergiraf/mergiraf/releases/download/v0.14.0/mergiraf_x86_64-unknown-linux-gnu.tgz I get a 404. We should probably specify `archive-suffix = ".tar.gz"` explicitly

wetneb commented

2025-09-03 16:30:50 +02:00

I also wondered about it. I tried it with cargo binstall --manifest-path . mergiraf@0.14.0 and it seemed to work like this, but I'm not opposed to adding it explicitly. We'll probably need to override it for windows then.

I also wondered about it. I tried it with `cargo binstall --manifest-path . mergiraf@0.14.0` and it seemed to work like this, but I'm not opposed to adding it explicitly. We'll probably need to override it for windows then.

ada4a commented

2025-09-09 14:05:26 +02:00

It looks like cargo-binstall does try to ping the .tar.gz version of the URL after .tgz fails, so it would eventually get to the correct link, but even during my short experimentation I started getting a bunch of "Too many requests" responses, so I think it's good to be more explicit, to both save time for the cargo-binstall users, and to avoid annoying Codeberg's servers too much.

It looks like `cargo-binstall` does try to ping the `.tar.gz` version of the URL after `.tgz` fails, so it would _eventually_ get to the correct link, but even during my short experimentation I started getting a bunch of "Too many requests" responses, so I think it's good to be more explicit, to both save time for the `cargo-binstall` users, and to avoid annoying Codeberg's servers too much.

ada4a marked this conversation as resolved

Cargo.toml Outdated

					
				@ -122,0 +124,4 @@

				pkg-url = "{ repo }/releases/download/v{ version }/{ name }_{ target }{ archive-suffix }"

				bin-dir = "{ bin }{ binary-ext }"

				pkg-fmt = "tgz"

				disabled-strategies = ["quick-install", "compile"]