Hello community,
here is the log from the commit of package rubygem-mime-types for
openSUSE:Factory checked in at 2013-10-21 12:59:08
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/rubygem-mime-types (Old)
and /work/SRC/openSUSE:Factory/.rubygem-mime-types.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "rubygem-mime-types"
Changes:
--------
--- /work/SRC/openSUSE:Factory/rubygem-mime-types/rubygem-mime-types.changes
2013-05-07 15:44:53.000000000 +0200
+++
/work/SRC/openSUSE:Factory/.rubygem-mime-types.new/rubygem-mime-types.changes
2013-10-21 12:59:09.000000000 +0200
@@ -1,0 +2,53 @@
+Tue Sep 3 08:10:13 UTC 2013 - [email protected]
+
+- updated to version 1.25
+ * New Features:
+ * Adding lazy loading and caching functionality to the default data based on
+ work done by Greg Brockman (gdb).
+ * Bugs:
+ * Force the default internal application encoding to be used when reading
the
+ MIME types database. Based on a change by briangamble, found in the rapid7
+ fork.
+ * New extensions:
+ * mjpeg (video/x-motion-jpeg) based on a change by punkrats, found in the
+ vidibus fork.
+ * Modernized MiniTest configuration.
+
+-------------------------------------------------------------------
+Mon Aug 26 05:05:24 UTC 2013 - [email protected]
+
+- updated to version 1.24
+ * Code Climate:
+ * Working on improving the quality of the mime-types codebase through the
use
+ of Code Climate. https://codeclimate.com/github/halostatue/mime-types
+ * Simplified MIME::Type.from_array to make more assumptions about
assignment.
+ * Documentation:
+ * LeoYoung <[email protected]> pointed out that the README.rdoc contained
+ examples that could never possibly work because MIME::Types#[] returns
(for
+ all the versions I have handy) an array, not a single type. I have updated
+ README.rdoc to reflect this.
+ * Removed Nokogiri as a declared development dependency. It is still required
+ if you're going to use the IANA parser functionality, but it is not
necessary
+ for most development purposes. This has been removed to ensure that Travis
CI
+ passes on Ruby 1.8.7.
+ * New MIME Types:
+ * 7zip (application/x-7z-compressed). Fixes a request by kodram.
+ https://github.com/halostatue/mime-types/issues/32
+ * application/x-www-form-urlencoded. Fixes a request by alexkwolfe.
+ https://github.com/halostatue/mime-types/issues/39
+ * Various new MIME types from IANA:
+ * application/mbms-schedule\+xml from 3GPP and Turcotte.
+ * application/provenance\+xml from W3C and Herman.
+ * application/session-info from 3GPP and Firmin.
+ * application/urc-grpsheet\+xml, application/urc-targetdesc\+xml,
+ application/uisocketdesc\+xml from Zimmermann.
+ * application/api\+json from Klabnik.
+ * application/vnd.etsi.pstn\+xml from Han and Belling.
+ * application/vnd.fujixerox.docuworks.container from Tashiro.
+ * application/vnd.windows.devicepairing from Dandawate.
+ * video/vnd.radgamettools.bink and video/vnd.radgamettools.smacker from
+ Andersson.
+ * Updated MIME Types:
+ * RFC 6960 was adopted (application/ocsp-request and
application/ocsp-response).
+
+-------------------------------------------------------------------
Old:
----
mime-types-1.23.gem
New:
----
mime-types-1.25.gem
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ rubygem-mime-types.spec ++++++
--- /var/tmp/diff_new_pack.52KtLR/_old 2013-10-21 12:59:10.000000000 +0200
+++ /var/tmp/diff_new_pack.52KtLR/_new 2013-10-21 12:59:10.000000000 +0200
@@ -17,7 +17,7 @@
Name: rubygem-mime-types
-Version: 1.23
+Version: 1.25
Release: 0
%define mod_name mime-types
%define mod_full_name %{mod_name}-%{version}
@@ -28,14 +28,37 @@
Url: http://mime-types.rubyforge.org/
Source: http://rubygems.org/gems/%{mod_full_name}.gem
Summary: This library allows for the identification of a file's likely
MIME
-License: MIT or (Artistic-1.0 or GPL-1.0+)
+License: MIT and Artistic-2.0 and GPL-2.0
Group: Development/Languages/Ruby
%description
This library allows for the identification of a file's likely MIME content
-type. This is release 1.23 that adds the ability to enumerate over the
-collection of MIME types and updates the sources of a few MIME types. The
-identification of MIME content type is based on a file's filename extensions.
+type. This is release 1.25, adding experimental caching and lazy loading
+functionality.
+The caching and lazy loading features were initially implemented by Greg
+Brockman (gdb). As these features are experimental, they are disabled by
+default and must be enabled through the use of environment variables. The
+cache
+is invalidated on a per-version basis; the cache for version 1.25 will not be
+reused for version 1.26.
+To use lazy loading, set the environment variable +RUBY_MIME_TYPES_LAZY_LOAD+
+to any value other than 'false'. When using lazy loading, the initial startup
+of MIME::Types is around 12–25× faster than normal startup (on my system,
+normal startup is about 90 ms; lazy startup is about 4 ms). This isn't
+generally useful, however, as the MIME::Types database has not been loaded.
+Lazy startup and load is just *slightly* faster—around 1 ms. The real
+advantage
+comes from using the cache.
+To enable the cache, set the environment variable +RUBY_MIME_TYPES_CACHE+ to a
+filename where MIME::Types will have read-write access. The first time a new
+version of MIME::Types is run using this file, it will be created, taking a
+little longer than normal. Subsequent loads using the same cache file will be
+approximately 3½× faster (25 ms) than normal loads. This can be combined with
++RUBY_MIME_TYPES_LAZY_LOAD+, but this is *not* recommended in a multithreaded
+or multiprocess environment where all threads or processes will be using the
+same cache file.
+As the caching interface is still experimental, the only values cached are the
+default MIME::Types database, not any custom MIME::Types added by users.
MIME types are used in MIME-compliant communications, as in e-mail or HTTP
traffic, to indicate the type of content which is transmitted. MIME::Types
provides the ability for detailed information about MIME entities (provided as
@@ -43,16 +66,14 @@
are many types defined by RFCs and vendors, so the list is long but not
complete; don't hesitate to ask to add additional information. This library
follows the IANA collection of MIME types (see below for reference).
-MIME::Types for Ruby was originally based on and synchronized with MIME::Types
-for Perl by Mark Overmeer, copyright 2001 - 2009. As of version 1.15, the data
-format for the MIME::Type list has changed and the synchronization will no
-longer happen.
+MIME::Types for Ruby was originally based on MIME::Types for Perl by Mark
+Overmeer, copyright 2001 - 2009. As of version 1.15, the data format for the
+MIME::Type list has changed and the synchronization will no longer happen.
MIME::Types is built to conform to the MIME types of RFCs 2045 and 2231. It
-follows the official {IANA
-registry}[http://www.iana.org/assignments/media-types/]
+tracks the {IANA registry}[http://www.iana.org/assignments/media-types/]
({ftp}[ftp://ftp.iana.org/assignments/media-types]) with some unofficial types
-added from the the {LTSW
-collection}[http://www.ltsw.se/knbase/internet/mime.htp].
+added from the {LTSW collection}[http://www.ltsw.se/knbase/internet/mime.htp]
+and added by the users of MIME::Types.
%package doc
Summary: RDoc documentation for %{mod_name}
@@ -80,9 +101,13 @@
%install
%gem_install -f
+mkdir -p %{buildroot}%{_docdir}/%{name}
+ln -s %{_libdir}/ruby/gems/%{rb_ver}/gems/%{mod_full_name}/History.rdoc
%buildroot/%{_docdir}/%{name}/History.rdoc
+ln -s %{_libdir}/ruby/gems/%{rb_ver}/gems/%{mod_full_name}/README.rdoc
%buildroot/%{_docdir}/%{name}/README.rdoc
%files
%defattr(-,root,root,-)
+%{_docdir}/%{name}
%{_libdir}/ruby/gems/%{rb_ver}/cache/%{mod_full_name}.gem
%{_libdir}/ruby/gems/%{rb_ver}/gems/%{mod_full_name}/
%exclude %{_libdir}/ruby/gems/%{rb_ver}/gems/%{mod_full_name}/test
--
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
