A fix for the mongo.gemspec dependency statement to prevent errors on older versions of Rubygems #93
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
banker
added a commit
that referenced
this pull request
Feb 28, 2012
Fix for the mongo.gemspec dependency statement to prevent errors on older versions of Rubygems.
|
awesome. Rookie question. What is the best way to reference this patch in my Gemfile? Will there be a new numbered release -- or should i point to the git commit in my Gemfile? Thanks! |
|
If all goes well, we'll release 1.6.1 today. |
|
@banker , any update on this? Thanks! |
|
@jtushman Should be in the latest release, 1.6.1. |
|
thanks -- i'll check it out! |
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.
As discussed on this commit which introduced this problem, if your
gemspecfile dependencies don't have a~>or>=or something to that effect, it can cause older versions ofrubygemsto throw errors. Newer versions of rubygems have a workaround for this error, but I'm not certain which version it was patched in.Read this blog post on Rubygems.org by Tenderlove for an in-depth explanation. As the gemfile sits currently, I cannot use the gem on Heroku due to the fact that their ruby environment is running
rubygems 1.3.7.