Hello community,

here is the log from the commit of package rubygem-nokogiri for 
openSUSE:Factory checked in at 2013-10-06 18:38:39
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/rubygem-nokogiri (Old)
 and      /work/SRC/openSUSE:Factory/.rubygem-nokogiri.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "rubygem-nokogiri"

Changes:
--------
--- /work/SRC/openSUSE:Factory/rubygem-nokogiri/rubygem-nokogiri.changes        
2013-07-02 07:44:45.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.rubygem-nokogiri.new/rubygem-nokogiri.changes   
2013-10-06 18:38:40.000000000 +0200
@@ -1,0 +2,5 @@
+Fri Oct  4 19:12:05 UTC 2013 - [email protected]
+
+- remove ports (libxml tar)
+
+-------------------------------------------------------------------

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ rubygem-nokogiri.spec ++++++
--- /var/tmp/diff_new_pack.E1QJla/_old  2013-10-06 18:38:41.000000000 +0200
+++ /var/tmp/diff_new_pack.E1QJla/_new  2013-10-06 18:38:41.000000000 +0200
@@ -28,10 +28,11 @@
 BuildRequires:  ruby-macros >= 1
 Requires:       ruby >= 1.9.2
 BuildRequires:  ruby-devel >= 1.9.2
-BuildRequires:  rubygem(rdoc) > 3.10
 BuildRequires:  rubygem(mini_portile)
+BuildRequires:  rubygem(rdoc) > 3.10
 # MANUAL
-BuildRequires:  libxml2-devel libxslt-devel
+BuildRequires:  libxml2-devel
+BuildRequires:  libxslt-devel
 Url:            http://nokogiri.org
 Source:         http://rubygems.org/gems/%{mod_full_name}.gem
 Summary:        Nokogiri (鋸) is an HTML, XML, SAX, and Reader parser
@@ -74,6 +75,7 @@
 %gem_install -f
 %gem_cleanup
 # MANUAL
+rm -rf %{buildroot}%{_libdir}/ruby/gems/%{rb_ver}/gems/%{mod_full_name}/ports
 mv %{buildroot}%{_bindir}/nokogiri{,%{mod_branch}}
 ln -s nokogiri%{mod_branch} %{buildroot}%{_bindir}/nokogiri
 mkdir -p %{buildroot}%{_docdir}/%{name}


-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to