Experimental support for SCL repositories on RHEL and CentOS #213
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
|
Need the squash PR with Travis-CI build passed =/ |
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.
This is in response to issue #189 and provides nominal support for SCL packages. I have only had a chance to test this with CentOS 6 and the python33 collection, so please treat this as experimental and intended to be a conversation starter, not a completely finished patch.
The module appears to function nominally correctly by setting python::provider to 'scl' and python::version to 'python33' (or whatever the name of the collection is).
I'm not sure pip is doing the correct thing -- RedHat in its wisdom declined to include a pip package in the RHEL 6 SCLs.