Skip to content

update cargo #355

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

Merged
merged 1 commit into from
May 13, 2019
Merged

update cargo #355

merged 1 commit into from
May 13, 2019

Conversation

QuietMisdreavus
Copy link
Member

Certain crates were not building on docs.rs because the Cargo it was using could not load in the futures-preview family of crates. After bringing it up on Discord, the Cargo team suggested that blindly loading cargo from master (if we must use it as a library at all) is problematic, and that we should use the commit that is currently loaded on rust-lang/rust master, to ensure that it's at least somewhat in sync with master. We should investigate fully removing our dependency on cargo as a library in favor of cargo metadata and calls to Cargo as a binary, to ensure that we don't run into situations like this again.

as suggested on discord, a sustainable method of selecting a version of
`cargo` to use is whatever commit is being used by rust-lang/rust. the
version selected in this commit uses the current version as of
2019-05-13.
@QuietMisdreavus QuietMisdreavus merged commit e608440 into rust-lang:master May 13, 2019
@QuietMisdreavus QuietMisdreavus deleted the new-cargo branch May 13, 2019 21:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant