Skip to content
This repository was archived by the owner on Nov 30, 2024. It is now read-only.

Conversation

@postmodern
Copy link
Contributor

  • This was necessary to get the specs running on ruby 2.0.0p353.

@myronmarston
Copy link
Member

I'm confused...json has been in the stdlib since 1.9. What's special about 2.0.0p353?

@JonRowe
Copy link
Member

JonRowe commented Apr 18, 2014

Indeed, and this has been running on Travis on 2.0.0 quite happily...

@postmodern
Copy link
Contributor Author

Ah I am using Fedora ruby which apparently moved json outside of stdlib.

@JonRowe
Copy link
Member

JonRowe commented Apr 18, 2014

Ah I am using Fedora ruby which apparently moved json outside of stdlib.

... this is like the RBX fiasco alllllll over again :), I see no harm in making this change, though perhaps we should file in issue with Fedora...

@postmodern
Copy link
Contributor Author

Actually, I just tested a vanilla version of ruby 2.0.0-p451 and bundler 1.6.2. Even those gem which json shows /opt/rubies/ruby-2.0.0-p451/lib/ruby/2.0.0/json.rb, bundler is not allowing me to require it.

Steps to Reproduce

  1. echo "source 'https://rubygems.org/'" > Gemfile
  2. bundle install
  3. bundle console
  4. require 'json'

This failed to load json under both Fedora's ruby 2.0 and vanilla ruby 2.0.

@JonRowe
Copy link
Member

JonRowe commented Apr 18, 2014

Isn't there an option for bundler that allows / disallows system gems?

@postmodern
Copy link
Contributor Author

Oops, my mistake. Rerunning the test confirms this is Fedora's fault. I will report upstream. In the meantime, it's up to you whether you want to always use a recent version of json.

@postmodern postmodern closed this Apr 18, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants