We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
cargo install --git
cargo version: cargo 0.21.0-nightly (4c0a8b63d 2017-06-27)
cargo 0.21.0-nightly (4c0a8b63d 2017-06-27)
It seems that currently cargo install --git( cargo install doesn't have this issue ) ignores Cargo.lock by default.
cargo install
Cargo.lock
Example project here would be ripgrep. Running this command:
ripgrep
RUSTFLAGS="-C target-cpu=native" cargo +nightly install --git https://github.com/BurntSushi/ripgrep.git --features 'simd-accel avx-accel'
will result in clap being picked with the version 2.25.0, which could of been a breaking API change, compared with the one included in Cargo.lock.
clap
2.25.0
If I clone the repo and build the project myself:
RUSTFLAGS="-C target-cpu=native" cargo +nightly build --release --features 'simd-accel avx-accel'
clap v2.24.1 is being picked-up from Cargo.lock.
clap v2.24.1
The text was updated successfully, but these errors were encountered:
This looks to be a subset of #7169 which has a lot more discussion. Closing in favor of that. If there was something I overlooked, let us know!
Sorry, something went wrong.
No branches or pull requests
cargo version:
cargo 0.21.0-nightly (4c0a8b63d 2017-06-27)
It seems that currently
cargo install --git
(cargo install
doesn't have this issue ) ignoresCargo.lock
by default.Example project here would be
ripgrep
.Running this command:
will result in
clap
being picked with the version2.25.0
, which could of been a breaking API change, compared with the one included inCargo.lock
.If I clone the repo and build the project myself:
clap v2.24.1
is being picked-up fromCargo.lock
.The text was updated successfully, but these errors were encountered: