Page MenuHomePhabricator

Support cargo-binstall for toolforge-rs binaries
Open, LowPublic

Description

cargo-binstall is a tool to try downloading Rust binaries from their repositories instead of compiling them locally, which can be slow. Metadata needs to be specified in Cargo.toml, see https://github.com/cargo-bins/cargo-binstall/blob/main/SUPPORT.md.

The toolforge crate publishes a "toolforge-tunnel" CLI, and CI automatically builds binaries when a tag is pushed: https://gitlab.wikimedia.org/repos/mwbot-rs/toolforge/-/releases. So for this task, we need to add the correct metadata in Cargo.toml so cargo-binstall can find the published binaries.


This is a good first task, let us know if you have any questions! Also take a look at mwbot-rs's contributing instructions.

Details

Related Changes in GitLab:
TitleReferenceAuthorSource BranchDest Branch
added metadata for cargo binstallrepos/mwbot-rs/toolforge!20jainlakshita28mainmain
Customize query in GitLab

Event Timeline

Legoktm triaged this task as Low priority.

Hello, I want to work on this issue. Can you please assign me this issue?

You can claim by youself, by clicking the Edit Task on the right of this page, add yourself to "Assignee" and save.

Jainlakshita28 set Due Date to Jan 26 2025, 12:00 AM.
Aklapper removed Due Date which was set to Jan 26 2025, 12:00 AM.Jan 19 2025, 9:04 AM

Hi, I tried to get developer access to project but it is saying to contact one of project lead. I raised this issue in project channel, they are saying to raise ticket on phabricator. I am new to open source development Can you help me with this issue? How to raise ticket or how to get developer access?

Hi. If your gitlab account is already activated, you could first click the fork button and push changes to your fork, then make a merge request to send your code for review. If not, you should follow the banner on gitlab.wikimedia.org to activate it.

image.png (664×192 px, 29 KB)

I have added the metadata, but i am getting this error while trying to use cargo binstall. Can you please help me to resolve this issue.

cargo binstall toolforge, probably. The crate is published on crates.io as toolforge instead of toolforge-tunnel.