Merged
Conversation
Contributor
|
I don't understand this PR. |
Member
Author
|
We agreed on closing #270 and continue publishing libhermit on crates.io without lockfile. Since no lockfile is present for downstream builds (downloading from crates.io), we should not maintain one in this repository as well. That way we build the same way when using this repository directly (like in CI) as when building downstream. |
9f3715d to
1f69688
Compare
1f69688 to
ba1658b
Compare
Contributor
|
bors r+ |
Contributor
|
Build failed: |
Member
Author
|
bors retry |
Contributor
|
Build failed: |
Member
Author
|
bors retry |
Contributor
|
Build failed: |
Member
Author
|
bors retry |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Since we use no
Cargo.lockin downstream builds, we should not use one in upstream CI either.