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

Make `cargo update` more conservative. #614

Merged
merged 1 commit into from Sep 22, 2014

Conversation

Projects
None yet
4 participants
@alexcrichton
Member

alexcrichton commented Sep 21, 2014

As described in #613, this commit switches the semantics of cargo update foo
to updating only foo, not any of its dependencies. A new flag,
--aggressive was added to restore the old behavior.

The behavior of attempting to only unlock foo, and then if resolve fails
unlock all dependencies of foo is unimplemented as it's not super relevant
right now when the majority of dependencies are git dependencies and resolution
cannot fail for version-related reasons.

Closes #613

Make `cargo update` more conservative.
As described in #613, this commit switches the semantics of `cargo update foo`
to updating *only* `foo`, not any of its dependencies. A new flag,
`--aggressive` was added to restore the old behavior.

The behavior of attempting to only unlock `foo`, and then if resolve fails
unlock all dependencies of `foo` is unimplemented as it's not super relevant
right now when the majority of dependencies are git dependencies and resolution
cannot fail for version-related reasons.

Closes #613
@brson

This comment has been minimized.

Show comment
Hide comment
@brson

brson commented on d1a332d Sep 22, 2014

r+

@wycats

This comment has been minimized.

Show comment
Hide comment
@wycats

wycats Sep 22, 2014

Contributor

r+

Contributor

wycats commented Sep 22, 2014

r+

@bors

This comment has been minimized.

Show comment
Hide comment
@bors

bors Sep 22, 2014

Contributor

saw approval from brson
at alexcrichton@d1a332d

Contributor

bors commented on d1a332d Sep 22, 2014

saw approval from brson
at alexcrichton@d1a332d

This comment has been minimized.

Show comment
Hide comment
@bors

bors Sep 22, 2014

Contributor

merging alexcrichton/cargo/issue-613 = d1a332d into auto-cargo

Contributor

bors replied Sep 22, 2014

merging alexcrichton/cargo/issue-613 = d1a332d into auto-cargo

This comment has been minimized.

Show comment
Hide comment
@bors

bors Sep 22, 2014

Contributor

alexcrichton/cargo/issue-613 = d1a332d merged ok, testing candidate = 262c794

Contributor

bors replied Sep 22, 2014

alexcrichton/cargo/issue-613 = d1a332d merged ok, testing candidate = 262c794

This comment has been minimized.

Show comment
Hide comment
@bors

bors Sep 22, 2014

Contributor

fast-forwarding master to auto-cargo = 262c794

Contributor

bors replied Sep 22, 2014

fast-forwarding master to auto-cargo = 262c794

bors added a commit that referenced this pull request Sep 22, 2014

auto merge of #614 : alexcrichton/cargo/issue-613, r=brson
As described in #613, this commit switches the semantics of `cargo update foo`
to updating *only* `foo`, not any of its dependencies. A new flag,
`--aggressive` was added to restore the old behavior.

The behavior of attempting to only unlock `foo`, and then if resolve fails
unlock all dependencies of `foo` is unimplemented as it's not super relevant
right now when the majority of dependencies are git dependencies and resolution
cannot fail for version-related reasons.

Closes #613

@bors bors merged commit d1a332d into rust-lang:master Sep 22, 2014

1 of 2 checks passed

continuous-integration/travis-ci The Travis CI build failed
Details
default all tests passed

@alexcrichton alexcrichton deleted the alexcrichton:issue-613 branch Sep 23, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment