easier patching for recipes#522
Merged
Merged
Conversation
Contributor
Author
|
Note that the recipe for vispy is broken - it attempts to apply two patches which do not exist. I kept it this way when converting the recipe, as I don't know what the patches do, or whether they aren't supposed to be in the recipe or the patch files just weren't added to a commit. Also, I didn't touch any of the python3-related recipes. |
Member
|
Thanks (and also for the others). |
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
2 participants
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.
Simplifies patching for recipes by removing boilerplate.