-
Notifications
You must be signed in to change notification settings - Fork 1
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
Upgrade to latest release #4
Comments
These changes sound great!
Which crates are you referring to here? If you are referring to moving binswap to cargo-binstall I would be happy to help in the process! |
Yes, I'm referring to Also, I think cargo-bins need more maintainers for these crates and I welcome any PR and anybody who want to be one. @passcod What's your thought on this? |
happy to |
@oeb25 Can you submit a PR to |
I was a bit busy and almost forgot about this 😂 |
cc @oeb25 Are you still intere in upstreaming this into cargo-binstall repository? I can give you maintainer role if you want. |
cc @oeb25 friendly ping on this issue, I really believe this should be maintained in cargo-binstall repository to make sure it gets all the updates of binstalk. |
In the latest release, we've refactored binstalk again and extract several crates out:
binstalk-registry
for fetching crates from crates.io or any custom registrybinstalk-fetchers
for actually fetching crates from releasebinstalk-bins
for installing binssimple-git
for cloning git repository directlycargo-toml-workspace
for loading manifest of any crate inside a workspaceWith that, you could remove
binstalk
and disable features that are unused and further customize the APIs.I also think it's good idea for such crates to be maintained in cargo-binstall repository since we would keep it up to date.
The text was updated successfully, but these errors were encountered: