feature: enable building git2-curl with vendored openssl #610
Conversation
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
|
Can you explain more why you would need this? In what scenario do you depend on git2-curl without also depending on git2? |
|
@ehuss Sorry about that you are right my fault. I am trying to update cargo-outdated to compile with vendored SSL. Something I recently did with with cargo-update. cargo-outdated depends on git2 directly where as cargo-outdated only depends on git2-curl. I was thinking I needed this but in reality it was just needed to build cargo itself with vendored-openssl as that is where the git2 dep is coming from |
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.
the main crate can be build with vendored ssl git2-curl can not. This adds that feature