smol readme change

This commit is contained in:
ryan 2020-12-14 21:47:43 +13:00
parent dd4407bbb6
commit 6bba72aead
2 changed files with 3 additions and 2 deletions

View file

@ -67,6 +67,7 @@ jobs:
- name: Install openssl (vcpkg) - name: Install openssl (vcpkg)
if: ${{ matrix.os == 'windows-latest' }} if: ${{ matrix.os == 'windows-latest' }}
timeout-minutes: 30
run: | run: |
vcpkg integrate install vcpkg integrate install
vcpkg install openssl:x64-windows-static vcpkg install openssl:x64-windows-static

View file

@ -1,6 +1,6 @@
# Cargo B(inary) Install # Cargo B(inary) Install
A helper for distributing / installing pre-built rust binaries in a pseudo-distributed and maybe-one-day secure manner. A helper for distributing / installing CI built rust binaries in a pseudo-distributed and maybe-one-day secure manner.
This is part experiment, part solving a personal problem, and part hope that we can solve / never re-visit this. Good luck! This is part experiment, part solving a personal problem, and part hope that we can solve / never re-visit this. Good luck!
## Status ## Status
@ -13,7 +13,7 @@ This is part experiment, part solving a personal problem, and part hope that we
## Getting Started ## Getting Started
First you'll need to install `cargo-binstall` either via `cargo install cargo-binstall` (and it'll have to compile, sorry...), or by grabbing a pre-compiled version from the [releases](https://github.com/ryankurte/cargo-binstall/releases) page and putting that on your path. It's like there's a problem we're trying to solve? First you'll need to install `cargo-binstall` either via `cargo install cargo-binstall` (and it'll have to compile, sorry...), or by grabbing a pre-compiled version from the [releases](https://github.com/ryankurte/cargo-binstall/releases) page and putting that somewhere on your path. It's like there's a problem we're trying to solve?
If a project supports `binstall` you can then install binaries via `cargo binstall NAME` where `NAME` is the name of the crate. We hope the defaults will work without configuration in _some_ cases, however, different projects have wildly different configurations. You may need to add some cargo metadata to support `binstall` in your project, see [Usage](#Usage) for details. If a project supports `binstall` you can then install binaries via `cargo binstall NAME` where `NAME` is the name of the crate. We hope the defaults will work without configuration in _some_ cases, however, different projects have wildly different configurations. You may need to add some cargo metadata to support `binstall` in your project, see [Usage](#Usage) for details.