-
-
Notifications
You must be signed in to change notification settings - Fork 99
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
Add homebrew/binstall/quickinstall support #31
Comments
Initial version is at https://nexte.st/book/pre-built-binaries.html -- super easy to install from that URL. |
Thanks for this! For the windows side, modern windows 10 ships both real curl and real tar. The only difference is you need to type curl.exe to avoid the poweshell alias "curl". |
@cwfitzgerald Got it, thanks! Any idea how to do the |
Not a clue! 😄 |
For windows, it would be possible to provide packages for scoop and or chocolatey. winget is provided by default in Windows 11 and available for Windows 10, but doesn't yet support standalone installation. |
Thanks @CAD97. Do you have experience with these? I don't really use Windows much these days so I'd really appreciate help creating whatever manifests etc need to be created. |
I've not made packages for any of these, so I don't have any advice to give beyond pointing at the official docs: |
I'd love to see |
@remoun would you like to take a stab at implementing it? Here's a first cut but it still likely needs to be tested out across OSes: https://gist.github.com/0840b338b7e2496615d897d915859dbf |
Added to Homebrew: #361 |
We now have binstall and homebrew support, and #369 tracks release signing. Closing as completed/with followups. |
Currently, the only way to install cargo-nextest is with the pre-built binaries, or by using
cargo install
. It would be nice to add other binary installation mechanisms as well.To consider:
Release signing(now tracked at Sign nextest's binary releases #369)Point people to cargo quickinstall(we already do our own binary releases now)The text was updated successfully, but these errors were encountered: