|author||dependabot-preview[bot] <dependabot-preview[bot]@users.noreply.github.com>||Fri May 24 17:05:39 2019 +0000|
|committer||dependabot-preview[bot] <dependabot-preview[bot]@users.noreply.github.com>||Fri May 24 17:27:51 2019 +0000|
Bump bstr from 0.1.3 to 0.1.4 Bumps [bstr](https://github.com/BurntSushi/bstr) from 0.1.3 to 0.1.4. - [Release notes](https://github.com/BurntSushi/bstr/releases) - [Commits](https://github.com/BurntSushi/bstr/compare/0.1.3...0.1.4)
Currently this can be installed with:
$ cargo install cargo-vendor
You can also install precompiled binaries that are assembled on the CI for this crate.
cargo vendor inside of any Cargo project:
$ cargo vendor add this to your .cargo/config for this project: [source.crates-io] replace-with = 'vendored-sources' [source.vendored-sources] directory = '/home/alex/code/cargo-vendor/vendor'
This will populate the
vendor directory which contains the source of all crates.io dependencies. When configured, Cargo will then use this directory instead of looking at crates.io.
Also note that the output of
cargo vendor that should be configuration is all on stdout (as opposed to stderr where other messages go), so you can also do:
$ cargo vendor > .cargo/config
to vendor and initialize your config in the same step!
If the vendored Cargo project makes use of
[replace] sections it can happen that the vendoring operation fails, e.g. with an error like this:
found duplicate version of package `libc v0.2.43` vendored from two sources: ...
--no-merge-sources should be able to solve that. Make sure to grab the
.cargo/config file directly from standard output since the config gets more complicated and unpredictable.
$ cargo vendor --no-merge-sources > .cargo/config
This project is licensed under either of
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in cargo-vendor by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.