Add explicit features for gix backend #824
Merged
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.
Update tame-index and integrate the latest change: EmbarkStudios/tame-index#66
This merge request is adding two features to allow downstream developers to select which gix backend to use. Since Rust unifies the feature of a crate when building it, and gix has two mutually exclusive features, the only way here seems to propagate this oddity and expose it in the features of this crate as well.
More concretely, this conflicts otherwise in our crate where we also pull in cargo which then always enables the curl backend.