Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: cargo-binstall compatible releases #10003

Open
0xdapper opened this issue Mar 4, 2025 · 1 comment
Open

feat: cargo-binstall compatible releases #10003

0xdapper opened this issue Mar 4, 2025 · 1 comment
Labels
A-releases Area: releases/packaging T-feature Type: feature

Comments

@0xdapper
Copy link
Contributor

0xdapper commented Mar 4, 2025

Component

Other (please describe)

Describe the feature you would like

cargo-binstall allows to install binaries with prebuilt binaries released in github/gitlab repo releases. There is already a nightly and stable release in the repo, but its not compatible with the format used by cargo-binstall. This can provide an alternate path to using foundryup if you didn't want to trust the foundryup script but trusted binstall.

From my limited research the release tars should be created per target(cast, forge, anvil, chisel) and the file name to be in certain format. This will also selective install of cast or forge instead of all of them. It is possible to add custom url formats, see here. I already tried to manually form a url with --pkg-url "{ repo }/releases/download/{ version }/foundry_{target-family}_{target-arch}_{archive-suffix}" but one of the main problems is it'd not allow stable or nightly to be passed as versions, needs semver crates like version.

Additional context

No response

@0xdapper 0xdapper added T-feature Type: feature T-needs-triage Type: this issue needs to be labelled labels Mar 4, 2025
@github-project-automation github-project-automation bot moved this to Todo in Foundry Mar 4, 2025
@zerosnacks zerosnacks added A-releases Area: releases/packaging T-blocked Type: blocked T-to-discuss Type: requires discussion and removed T-needs-triage Type: this issue needs to be labelled T-blocked Type: blocked T-to-discuss Type: requires discussion labels Mar 4, 2025
@0xscharki
Copy link

Could I take a shot at this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-releases Area: releases/packaging T-feature Type: feature
Projects
Status: Todo
Development

No branches or pull requests

3 participants