From: Lazaridis Ilias <ilias@...>
Date: 2011-05-26T16:56:32+09:00
Subject: [ruby-core:36485] [Ruby 1.9 - Feature #4784] Import the JSON library


Issue #4784 has been updated by Lazaridis Ilias.


Sakuro OZAWA wrote:
> $ ls path-to/ruby/1.9.1/json*
>  path-to/ruby/1.9.1/json.rb
>  
>  path-to/ruby/1.9.1/json:
>  add/  common.rb  ext.rb  version.rb
> 
> >dm-serializer requires json 1.4.6
> 
> this means dm-serializer uses JSON *gem* for JSON parsing so it can run both on 1.8 (where json library is not bundled) and 1.9.

Actually this means that although ruby 1.9 *could* resolve the requirement, it does not do so.

Solution could be:

 * Either ruby should signal "I have json code similar to gem x.x.x", or 
 * the gem system should be told that 1.9 contains code which is equal to "json x.x.x"
 
> You must distinguish gem from bundled library.

I could even do this (although I've another technical view of this), but what about a simple user?

You should really take care of all this.

It's possibly as simple as asking the json maintainer to give access to the repos, thus the gems binaries can be build:

https://github.com/flori/json/issues/75






----------------------------------------
Feature #4784: Import the JSON library
http://redmine.ruby-lang.org/issues/4784

Author: Lazaridis Ilias
Status: Rejected
Priority: Normal
Assignee: 
Category: ext
Target version: 


I've personally lost several hours with the JSON gem (and was still not able to resolve the problem in a way that is acceptable for end-users).

The JSON library is an important library.

It should be included into ruby 1.9, thus it works "out-of-the-box" on all platforms.

If this is for any reason not possible, then there should be some kind of "caretaker".

This means that one ruby developer takes care about the sanity of the JSON gem.

This could be e.g. the developer who is responsible for YAML (as yaml/json are somehow related).




-- 
http://redmine.ruby-lang.org