Hello community,
here is the log from the commit of package rubygem-mime-types for
openSUSE:Factory checked in at 2015-12-14 10:13:48
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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
2015-09-27 08:38:49.000000000 +0200
+++
/work/SRC/openSUSE:Factory/.rubygem-mime-types.new/rubygem-mime-types.changes
2015-12-14 10:13:48.000000000 +0100
@@ -1,0 +2,82 @@
+Sun Nov 22 05:38:25 UTC 2015 - [email protected]
+
+- updated to version 3.0
+ see installed History.rdoc
+
+ == 3.0 / 2015-11-21
+
+ * 2 governance changes
+
+ * This project and the related mime-types-data project are now exclusively
+ MIT licensed. Resolves
+ {#95}[https://github.com/mime-types/ruby-mime-types/issues/95].
+
+ * All projects under the mime-types organization now have a standard code
of
+ conduct adapted from the {Contributor
+ Covenant}[http://contributor-covenant.org]. This text can be found in the
+ {Code-of-Conduct.rdoc}[Code-of-Conduct_rdoc.html] file.
+
+ * 3 major changes
+
+ * All methods deprecated in mime-types 2.x have been removed.
+ * mime-types now requires Ruby 2.0 compatibility or later. Resolves
+ {#97}[https://github.com/mime-types/ruby-mime-types/issues/97].
+ * The registry data has been removed from mime-types and put into
+ mime-types-data, maintained and released separately. It can be found at
+ {mime-types-data}[https://github.com/mime-types/mime-types-data].
+
+ * 17 minor changes:
+
+ * MIME::Type changes:
+
+ * Changed the way that simplified types representations are creatd to
+ reflect the fact that +x-+ prefixes are no longer considered special
+ according to IANA. A simplified MIME type is case-folded to lowercase.
A
+ new keyword parameter, +remove_x_prefix+, can be provided to remove
+x-+
+ prefixes.
+ * Improved initialization with an Array works so that extensions do not
+ need to be wrapped in another array. This means that <tt>%w(text/yaml
+ yaml yml)</tt> works in the same way that <tt>['text/yaml', %w(yaml
+ yml)]</tt> did (and still does).
+ * Changed +priority_compare+ to conform with attributes that no longer
+ exist.
+ * Changed the internal implementation of extensions to use a frozen Set.
+ * When extensions are set or modified with +add_extensions+, the primary
+ registry will be informed of a need to reindex extensions. Resolves
+ {#84}[https://github.com/mime-types/ruby-mime-types/issues/84].
+ * The preferred extension can be set explicitly. If not set, it will be
the
+ first extension. If the preferred extension is not in the extension
list,
+ it will be added.
+ * Improved how xref URLs are generated.
+ * Converted +obsolete+, +registered+ and +signature+ to attr_accessors.
+
+ * MIME::Types changes:
+
+ * Modified MIME::Types.new to track instances of MIME::Types so that they
+ can be told to reindex the extensions as necessary.
+ * Removed +data_version+ attribute.
+ * Changed #[] so that the +complete+ and +registered+ flags are keywords
+ instead of a generic options parameter.
+ * Extracted the class methods to a separate file.
+ * Changed the container implementation to use a Set instead of an Array
to
+ prevent data duplication. Resolves
+ {#79}[https://github.com/mime-types/ruby-mime-types/issues/79].
+
+ * MIME::Types::Cache changes:
+
+ * Caching is now based on the data gem version instead of the mime-types
+ version.
+ * Caching is compatible with columnar registry stores.
+
+ * MIME::Types::Loader changes:
+
+ * MIME::Types::Loader::PATH has been removed and replaced with
+ MIME::Types::Data::PATH from the mime-types-data gem. The environment
+ variable RUBY_MIME_TYPES_DATA is still used.
+ * Support for the long-deprecated mime-types v1 format has been removed.
+ * The registry is default loaded from the columnar store by default. The
+ internal format of the columnar store has changed; many of the boolean
+ flags are now loaded from a single file. Resolves
+ {#85}[https://github.com/mime-types/ruby-mime-types/85].
+
+-------------------------------------------------------------------
Old:
----
mime-types-2.6.2.gem
New:
----
mime-types-3.0.gem
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ rubygem-mime-types.spec ++++++
--- /var/tmp/diff_new_pack.i7QtJ2/_old 2015-12-14 10:13:49.000000000 +0100
+++ /var/tmp/diff_new_pack.i7QtJ2/_new 2015-12-14 10:13:49.000000000 +0100
@@ -24,12 +24,12 @@
#
Name: rubygem-mime-types
-Version: 2.6.2
+Version: 3.0
Release: 0
%define mod_name mime-types
%define mod_full_name %{mod_name}-%{version}
BuildRoot: %{_tmppath}/%{name}-%{version}-build
-BuildRequires: %{ruby >= 1.9.2}
+BuildRequires: %{ruby >= 2.0}
BuildRequires: %{rubygem gem2rpm}
BuildRequires: %{rubygem rdoc > 3.10}
BuildRequires: ruby-macros >= 5
@@ -37,7 +37,7 @@
Source: http://rubygems.org/gems/%{mod_full_name}.gem
Source1: gem2rpm.yml
Summary: The mime-types library provides a library and registry for
-License: MIT and Artistic-2.0 and GPL-2.0
+License: MIT
Group: Development/Languages/Ruby
%description
@@ -45,29 +45,15 @@
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. There are many types defined by RFCs and vendors, so the
-list is long but by definition incomplete; don't hesitate to add additional
-type definitions. MIME type definitions found in mime-types are from RFCs, W3C
-recommendations, the {IANA Media Types
-registry}[https://www.iana.org/assignments/media-types/media-types.xhtml], and
-user contributions. It conforms to RFCs 2045 and 2231.
-This is release 2.6 with two new experimental features. The first new feature
-is a new default registry storage format that greatly reduces the initial
-memory use of the mime-types library. This feature is enabled by requiring
-+mime/types/columnar+ instead of +mime/types+ with a small performance cost
-and
-no change in *total* memory use if certain methods are called (see {Columnar
-Store}[#label-Columnar+Store]). The second new feature is a logger interface
-that conforms to the expectations of an ActiveSupport::Logger so that warnings
-can be written to an application's log rather than the default location for
-+warn+. This interface may be used for other logging purposes in the future.
-mime-types 2.6 is the last planned version of mime-types 2.x, so deprecation
-warnings are no longer cached but provided every time the method is called.
-mime-types 2.6 supports Ruby 1.9.2 or later.
+Version 3.0 is a major release that requires Ruby 2.0 compatibility and
+removes
+deprecated functions. The columnar registry format introduced in 2.6 has been
+made the primary format; the registry data has been extracted from this
+library
+and put into {mime-types-data}[https://github.com/mime-types/mime-types-data].
+Additionally, mime-types is now licensed exclusively under the MIT licence and
+there is a code of conduct in effect. There are a number of other smaller
+changes described in the History file.
%prep
++++++ mime-types-2.6.2.gem -> mime-types-3.0.gem ++++++
++++ 27795 lines of diff (skipped)
