mime-types 2.4.2 → 2.4.3

checksums.yaml

@@ -1,15 +1,15 @@
 ---
 !binary "U0hBMQ==":
   metadata.gz: !binary |-
-    MWViMWFhNWYxYmU3ZjM1NmE4ODUwNzM4ZjFlNDU1NjY0MTJhODBjMA==
+    ZjcwYmQxOTg1ZjdmOTI4Zjk3OTRlYzdlZWU1MWY5OTM4M2M5NzdlMQ==
   data.tar.gz: !binary |-
-    YmNmY2UyMDhkYjk0ZmE2NTE0MjI2ZWMxNjJmYzY4YjgwZTRkY2E5ZA==
+    N2IzN2QyZmUwMTJlNWI4ZjM3MzFjODYwNGI5NTgzYmQ3YmExN2ExMg==
 SHA512:
   metadata.gz: !binary |-
-    NTExNDY1MzFlNmFhMDU5NWQxMTEzZTY2YzE2ZWNlMjkzY2VmNzZmZjI3NGQ4
-    YmRmNjQ3NzY0YzA0ODhmNzEzZTc2N2E4NDg5NWI2NjczNjQ0Nzg3NDY4Njkz
-    OTlhNGVkNzBlYzcyZGU0MWVjNTk0NjMzNjhiOGRhZGI3YWZiY2I=
+    ZDQ3M2FkYWI3MDkyM2JlMTE1NDM2Y2Q2Y2Q1NGRlNTRlYmNlYTQ4MDZjODYy
+    YjRlZTNmYjZkYzE5ODA2YWJkZmU5MTE1ZGFkNjUxOTkzYjg4NmM0MGI5Nzcz
+    ZmVlNDM0MDExZDgwOWY4ZTA1ZmM2YTZlZjdjNmZhMzVlMzU0YTU=
   data.tar.gz: !binary |-
-    YTZiMDRlYzljMDk4MDRjZTA0MGJhMWFhMTU1YWIyNTQ1MDc4YTkzOTVkYjg4
-    MGVhYTZlODU2MDEzOTBiOTc0ZTIxYzhiMmQ1MDhjNGUwNWQ5ZTA0NDY1YThj
-    MWYzYTBiNTk4NDQzMzFjNjk3MzMwM2Q0MTUwNzVkM2YyNDY5Yjk=
+    ZmVlNjRjY2RhNjIxM2IwY2FiZTAwZjYzOWY1MjJkMGU1N2RiM2YyMzcxYTZh
+    YWZmYWI0ODBlM2JkOTg0M2RhMjVlOTc1Mzk3YjA2Y2Y5NzNjMWVjNzJlNDRi
+    N2E3NWViMzliZGJhOTI2OTg3NzkyNTEwODIwMWRiZDllNzc3Njc=

data.tar.gz.sig

@@ -1 +1 @@
-jbʫ�<S0F_�.US����v��-�q���F{M�E�/+;��5Z�%-�W�l˖}�ҍf�2�>i�'.��':6���t_��Կ�Y9�y-�ݿ�F߻r\Ȟ�.�ª{.p{�|K!p�*u�F(�a韥sC{N���)��c�a�I3` ���oR�Q[8�k�a�C�)�Ձ_&��I�%��h�ȝ�q
Nc9�[U1��Dzk)Ud��#u�
p���/�*�6L�/�}�m�Ja��Yn����-ƥ��
+

data/History.rdoc

@@ -1,3 +1,12 @@
+== 2.4.3 / 2014-10-21
+
+* Bugs:
+  * Restored Ruby 1.9.2 support by using +private_constant+ conditionally.
+    Fixes {#77}[https://github.com/halostatue/mime-types/issues/77] found by
+    Kris Leech (@krisleech). The conditional use of +private_constant+ here
+    will be removed for mime-types 3.0, when Ruby 1.9.2 support will be
+    unconditionally removed.
+
 == 2.4.2 / 2014-10-15
 
 * Bugs:

data/README.rdoc

@@ -24,12 +24,11 @@ add additional type definitions (see Contributing.rdoc). The primary sources
 for MIME type definitions found in mime-types is the IANA collection of
 registrations (see below for the link), RFCs, and W3C recommendations.
 
-This is release 2.4.2, fixing bugs with unnecessary object duplication and
-using JSON.parse instead of JSON.load. These fixes improve the JSON registry
-loading time by about 55% over previous 2.x releases. Cached registry load
-times are not changed. This release builds on the 2.4.1 release, which fixed a
-bug in observed use of the mime-types library where extensions were not
-previously sorted, such that
+This is release 2.4.3, restoring full compatibility with Ruby 1.9.2 (which will
+be dropped in mime-types 3.0). It also includes the performance improvements
+from mime-types 2.4.2 (since yanked because of the broken Ruby 1.9.2 support)
+and the 2.4.1 fix of a bug in observed use of the mime-types library where
+extensions were not previously sorted, such that
 
     MIME::Types.of('image.jpg').first.extensions.first
 

data/lib/mime/type.rb

@@ -56,7 +56,7 @@ class MIME::Type
   end
 
   # The released version of the mime-types library.
-  VERSION = '2.4.2'
+  VERSION = '2.4.3'
 
   include Comparable
 
@@ -74,9 +74,12 @@ class MIME::Type
   RFC_URL           = "http://rfc-editor.org/rfc/rfc%s.txt"
   DRAFT_URL         = "http://datatracker.ietf.org/public/idindex.cgi?command=id_details&filename=%s"
   CONTACT_URL       = "http://www.iana.org/assignments/contact-people.htm#%s"
-  private_constant :MEDIA_TYPE_RE, :UNREGISTERED_RE, :I18N_RE, :PLATFORM_RE,
-    :DEFAULT_ENCODINGS, :BINARY_ENCODINGS, :TEXT_ENCODINGS, :VALID_ENCODINGS,
-    :IANA_URL, :RFC_URL, :DRAFT_URL, :CONTACT_URL
+
+  if respond_to? :private_constant
+    private_constant :MEDIA_TYPE_RE, :UNREGISTERED_RE, :I18N_RE, :PLATFORM_RE,
+      :DEFAULT_ENCODINGS, :BINARY_ENCODINGS, :TEXT_ENCODINGS, :VALID_ENCODINGS,
+      :IANA_URL, :RFC_URL, :DRAFT_URL, :CONTACT_URL
+  end
 
   # Builds a MIME::Type object from the provided MIME Content Type value
   # (e.g., 'text/plain' or 'applicaton/x-eruby'). The constructed object is

data/lib/mime/types/loader.rb

@@ -235,5 +235,6 @@ class MIME::Types::Loader
     \s*
     \z
     }x
-  private_constant :V1_FORMAT
+
+  private_constant :V1_FORMAT if respond_to? :private_constant
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: mime-types
 version: !ruby/object:Gem::Version
-  version: 2.4.2
+  version: 2.4.3
 platform: ruby
 authors:
 - Austin Ziegler
@@ -36,7 +36,7 @@ cert_chain:
   SHkzay9FVEZoaSs3cElVV2xGbzBpbXJkeUxoZCtKdzNib1ZqM0NtdnloY3dt
   cG9NMEs5bApBT21yVWlFbFVxTE9aQT09Ci0tLS0tRU5EIENFUlRJRklDQVRF
   LS0tLS0K
-date: 2014-10-15 00:00:00.000000000 Z
+date: 2014-10-21 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: minitest
@@ -203,11 +203,11 @@ description: ! "The mime-types library provides a library and registry for infor
   incomplete; don't hesitate to to\nadd additional type definitions (see Contributing.rdoc).
   The primary sources\nfor MIME type definitions found in mime-types is the IANA collection
   of\nregistrations (see below for the link), RFCs, and W3C recommendations.\n\nThis
-  is release 2.4.2, fixing bugs with unnecessary object duplication and\nusing JSON.parse
-  instead of JSON.load. These fixes improve the JSON registry\nloading time by about
-  55% over previous 2.x releases. Cached registry load\ntimes are not changed. This
-  release builds on the 2.4.1 release, which fixed a\nbug in observed use of the mime-types
-  library where extensions were not\npreviously sorted, such that\n\n    MIME::Types.of('image.jpg').first.extensions.first\n\nreturned
+  is release 2.4.3, restoring full compatibility with Ruby 1.9.2 (which will\nbe dropped
+  in mime-types 3.0). It also includes the performance improvements\nfrom mime-types
+  2.4.2 (since yanked because of the broken Ruby 1.9.2 support)\nand the 2.4.1 fix
+  of a bug in observed use of the mime-types library where\nextensions were not previously
+  sorted, such that\n\n    MIME::Types.of('image.jpg').first.extensions.first\n\nreturned
   a value of +jpeg+ in mime-types 1, but +jpe+ in mime-types 2. This was\nintroduced
   because extensions were sorted during assignment\n(MIME::Type#extensions=). This
   behaviour has been reverted to protect clients\nthat work as noted above. The preferred