Hello community,
here is the log from the commit of package rubygem-mime-types for
openSUSE:Factory checked in at 2013-11-07 08:46:22
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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-10-21 12:59:09.000000000 +0200
+++
/work/SRC/openSUSE:Factory/.rubygem-mime-types.new/rubygem-mime-types.changes
2013-11-07 08:46:23.000000000 +0100
@@ -1,0 +2,68 @@
+Thu Oct 31 05:54:42 UTC 2013 - [email protected]
+
+- updated to version 2.0, see History.rdoc
+
+ * API Changes (General):
+ * mime-types is no longer compatible with Ruby 1.8. Additionally, for its
+ YAML operations (normally development and test), it requires a YAML parser
+ that conforms to the Psych parser, not the Syck parser. This would only be
+ a problem with an alternative Ruby 1.9.2 interpreter that does not
+ implement the Psych parser conventions by requiring +psych+.
+ * MIME::InvalidContentType has been renamed to
+ MIME::Type::InvalidContentType.
+ * API Changes (MIME::Type):
+ * Construction of a MIME::Type can be with any of the following objects:
+ * An array containing a valid content type identifier and an optional
array
+ of extensions. This allows MIME::Type.new to be used instead of
+ MIME::Type.from_array for the most common use-case. Fixes #43.
+ https://github.com/halostatue/mime-types/pull/43
+ * A Hash containing the output of MIME::Type#to_h, as would be
deserialized
+ from the JSON representation of a MIME::Type. This replaces
+ MIME::Type.from_hash using a different parameter set.
+ * Another MIME::Type.
+ * A content type identifier string.
+ * Assignment of an invalid encoding to MIME::Type#encoding= will raise a
+ MIME::Type::InvalidEncoding exception rather than a plain ArgumentError.
+ * MIME::Type#url has been renamed to MIME::Type#references.
+ * MIME::Type#use_instead is now tracked as its own attribute, not as part of
+ MIME::Type#docs.
+ * MIME::Type#system, MIME::Type#system?, MIME::Type#platform?,
+ MIME::Type#to_a, MIME::Type#to_hash, MIME::Type.from_array,
+ MIME::Type.from_hash, and MIME::Type.from_mime_type have been deprecated
+ for removal.
+ * Implemented YAML object encoding and decoding methods,
+ MIME::Type#encode_with and MIME::Type#init_with.
+ * Implemented JSON hash encoding methods.
+ * Added MIME::Type#add_extensions to easily add extensions to a MIME::Type.
+ Fixes #44. https://github.com/halostatue/mime-types/pull/44
+ * API Changes (MIME::Types):
+ * MIME type caching has been extracted to its own class. It is structurally
+ similar to what was introduced with mime-types 1.25, but is no longer
+ considered an experimental interface.
+ * MIME type loading has been extracted to its own class. Loading has changed
+ substantially.
+ * MIME::Types#[] accepts a new filter flag, :registered. The :platform flag
+ has been deprecated.
+ * The MIME::Types#type_for platform parameter has been deprecated.
+ * Added the ability for MIME::Types#type_for produce results for multiple
+ filenames or extensions by providing an array as the first parameter.
Fixes
+ #42. https://github.com/halostatue/mime-types/pull/42
+ * MIME::Types#add_type_variant and MIME::Types#index_extensions have been
+ deprecated as public methods. They will be private in a future version.
+ * MIME::Types#defined_types, MIME::Types.cache_file,
+ MIME::Types.add_type_variant, and MIME::Types.index_extensions have been
+ deprecated for removal.
+ * Default Registry Changes:
+ * The default registry is now a file in the directory data/, located via
+ MIME::Types::Loader::PATH. +PATH+ is defined in the file
+ lib/mime/types/path.rb so that system packagers only have to modify one
+ file in order to put the registry in a location that is not where a gem
+ version of mime-types would expect it. This resolves issue #36, reported
by
+ postmodern. https://github.com/halostatue/mime-types/pull/36
+ * The default registry is now a single file in JSON format. This resolves
+ issue #28 reported by jasonlor (an error with mime-types in MacRuby).
+ https://github.com/halostatue/mime-types/pull/28
+ * The default registry is compiled from YAML files in type-lists/, resolving
+ issue #37 reported by postmodern requesting an easier-to-edit format.
+
+-------------------------------------------------------------------
Old:
----
mime-types-1.25.gem
New:
----
mime-types-2.0.gem
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ rubygem-mime-types.spec ++++++
--- /var/tmp/diff_new_pack.MfTIWT/_old 2013-11-07 08:46:23.000000000 +0100
+++ /var/tmp/diff_new_pack.MfTIWT/_new 2013-11-07 08:46:23.000000000 +0100
@@ -17,63 +17,49 @@
Name: rubygem-mime-types
-Version: 1.25
+Version: 2.0
Release: 0
%define mod_name mime-types
%define mod_full_name %{mod_name}-%{version}
BuildRoot: %{_tmppath}/%{name}-%{version}-build
BuildRequires: ruby-macros >= 1
+Requires: ruby >= 1.9.2
+BuildRequires: ruby-devel >= 1.9.2
BuildRequires: rubygem(rdoc) > 3.10
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
+Summary: The mime-types library provides a library and registry for
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.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
-a set of MIME::Type objects) to be determined and used programmatically. There
-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 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
-tracks the {IANA registry}[http://www.iana.org/assignments/media-types/]
+The mime-types library provides a library and registry for information about
+MIME content type definitions. It can be used to determine defined filename
+extensions for MIME types, or to use filename extensions to look up the likely
+MIME type definitions.
+MIME content types are used in MIME-compliant communications, as in e-mail or
+HTTP traffic, to indicate the type of content which is transmitted. The
+mime-types library provides the ability for detailed information about MIME
+entities (provided as an enumerable collection of MIME::Type objects) to be
+determined and used programmatically. There are many types defined by RFCs and
+vendors, so the list is long but by definition incomplete; don't hesitate to
+to
+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.
+The mime-types library uses semantic versioning. This is release 2.0; there
+are
+incompatible changes in the API provided by mime-types, mostly around registry
+initialization (see History.rdoc for full details), and the removal of support
+for Ruby 1.8 interpreters.
+mime-types (previously called MIME::Types for Ruby) was originally based on
+MIME::Types for Perl by Mark Overmeer, copyright 2001 - 2009. It is built to
+conform to the MIME types of RFCs 2045 and 2231. It 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 {LTSW collection}[http://www.ltsw.se/knbase/internet/mime.htp]
-and added by the users of MIME::Types.
+and added by the users of mime-types.
%package doc
Summary: RDoc documentation for %{mod_name}
--
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
