Red Hat Bugzilla – Bug 905389
Review Request: rubygem-json15 - JSON implementation in Ruby (version 1.5.x)
Last modified: 2013-02-04 08:02:45 EST
Spec URL: http://users.linpro.no/ingvar/vagrant/f18/specs/rubygem-json15.spec
SRPM URL: http://users.linpro.no/ingvar/vagrant/f18/src/rubygem-json15-1.5.4-1.fc18.src.rpm
In my quest to build a native package of vagrant, I needed rubygem-json-1.5.x. Current Fedoras have moved past this months ago (atm, f18 has 1.6.5, rawhide has 1.7.5). So I wrapped a versioned package rubygem-json15.
The package description will be the same as in the current version:
This is a implementation of the JSON specification according
to RFC 4627 in Ruby.
You can think of it as a low fat alternative to XML,
if you want to store data to disk or transmit it over
a network rather than use a verbose markup language.
See also #905240
Fedora Account System Username: ingvar
I am wondering if there is any reason to not move to the latest json, except that something is written in vagrant's .gemspec file? Have you tried to ask upstream and possibly solve this issue?
Also, if this is intended to be dependency of vagrant, it might be useful to make this issue block the vagrant review.
I have no other use for this package than as a requisite for vagrant, #905396.
Next upstream release of vagrant will have fixed this. Current git master can use the json gem that is in f18.
So, should I just wait for upstream?
(In reply to comment #2)
> I have no other use for this package than as a requisite for vagrant,
> Next upstream release of vagrant will have fixed this. Current git master
> can use the json gem that is in f18.
> So, should I just wait for upstream?
I would say this is the best option (or push upstream a bit to release what they have :). Or backport relevant patches, but you might get into troubles due to bundler.
Okay, I've moved to upstream development version of vagrant, and will follow till it releases. Closing this now as wontfix.