Remove dependency to "mini_portile2" from binary gems #1989
Conversation
This file contains 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
It is only necessary at build in extconf.rb.
|
Thank you, @larskanis! |
|
@larskanis 🤔 This change doesn't seem to have any effect. I don't see the |
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.
It is only necessary at build in extconf.rb.
What problem is this PR intended to solve?
As noted in this issue binary gems depend on "mini_portile2" gems, although it isn't necessary.
Have you included adequate test coverage?
There are no automated tests for binary gems, so far.
Does this change affect the C or the Java implementations?
Only the C implementation.