`require': no such file to load -- open3_backport (LoadError) #167
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
|
Not particularly happy to install a gem at runtime but it only affects 1.8 users. Could have the same problem with the json gem |
carlossg
added a commit
that referenced
this pull request
Jan 20, 2014
`require': no such file to load -- open3_backport (LoadError)
carlossg
pushed a commit
that referenced
this pull request
Feb 11, 2014
…not present" This reverts commit 89ae7f2.
carlossg
pushed a commit
that referenced
this pull request
Feb 11, 2014
…not present" This reverts commit 89ae7f2.
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.
Copied from maestrodev#16 (was raised for librarian-puppet-maestrodev but looks like it would affect this as well)
Hello,
I have a failure in Travis on Ruby 1.8.7 - the open3_backport gem isn't being installed. This appears to be due to the gemspec conditionally adding this as a dependency, but it's evaluated at build time, not install time, so the dependency isn't added to Ruby < 1.9 installs.
Apparently this is the required approach: http://en.wikibooks.org/wiki/Ruby_Programming/RubyGems#How_to_install_different_versions_of_gems_depending_on_which_version_of_ruby_the_installee_is_using
References: