ruby-multi_json

Branch :

Log

Commit	Date	Message
9fe1e38b	2019-07-12 20:43:27	replace simple PERMIT_PACKAGE_CDROM=Yes with PERMIT_PACKAGE=Yes
6c21dd98	2016-01-10 17:35:11	update to multi_json-1.11.2
36b686f4	2015-06-17 18:51:15	update to multi_json-1.11.1
507fe202	2015-03-16 07:20:49	Update multi_json to 1.11.0, which fixes a problem with aws-sdk-core rubygem for me. OK jeremy@, jasper@
570aa62a	2015-01-18 03:12:39	Drop remaining MD5/RMD160/SHA1 checksums.
e79a176b	2013-10-26 23:55:34	Bump all ruby gem ports supporting rbx FLAVOR due to change to rubinius gem directory when upgrading rubinius from 1.2.4 to 2.1.1.
51e3b5bd	2013-03-11 01:30:26	PERMIT_* / REGRESS->TEST sweep
c3579f1b	2012-09-23 16:57:32	Bump revisions for ruby gem/extconf ports after the switch to ruby 1.9 by default, since the ruby 1.8 version now has a ruby18 explicit FLAVOR.
4ef648d6	2011-12-13 17:33:30	Import ruby-multi-json 1.0.3, a Rails 3.1 dependency Lots of Ruby libraries utilize JSON parsing in some form, and everyone has their favorite JSON library. In order to best support multiple JSON parsers and libraries, multi_json is a general-purpose swappable JSON backend library. MultiJSON tries to have intelligent defaulting. That is, if you have any of the supported engines already loaded, it will utilize them before attempting to load any. When loading, libraries are ordered by speed. First Yajl-Ruby, then the JSON gem, then JSON pure. If no JSON library is available, MultiJSON falls back to a bundled version of OkJson. OK claudio@