Hello community,

here is the log from the commit of package rubygem-uglifier for 
openSUSE:Factory checked in at 2013-05-17 08:35:15
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/rubygem-uglifier (Old)
 and      /work/SRC/openSUSE:Factory/.rubygem-uglifier.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "rubygem-uglifier"

Changes:
--------
--- /work/SRC/openSUSE:Factory/rubygem-uglifier/rubygem-uglifier.changes        
2013-04-20 18:02:40.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.rubygem-uglifier.new/rubygem-uglifier.changes   
2013-05-17 08:35:16.000000000 +0200
@@ -1,0 +2,8 @@
+Thu May  9 16:39:50 UTC 2013 - [email protected]
+
+- updated to version 2.1.0
+   - update to UglifyJS 2.3.0
+   - add enclose and screw_ie8 options
+   - fix compatibility with Sprockets 2.9.0
+
+-------------------------------------------------------------------

Old:
----
  uglifier-2.0.1.gem

New:
----
  uglifier-2.1.0.gem

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

Other differences:
------------------
++++++ rubygem-uglifier.spec ++++++
--- /var/tmp/diff_new_pack.tG9ZeM/_old  2013-05-17 08:35:17.000000000 +0200
+++ /var/tmp/diff_new_pack.tG9ZeM/_new  2013-05-17 08:35:17.000000000 +0200
@@ -17,7 +17,7 @@
 
 
 Name:           rubygem-uglifier
-Version:        2.0.1
+Version:        2.1.0
 Release:        0
 %define mod_name uglifier
 %define mod_full_name %{mod_name}-%{version}
@@ -59,9 +59,12 @@
 
 %install
 %gem_install -f
+mkdir -p %{buildroot}%{_docdir}/%{name}
+ln -s %{_libdir}/ruby/gems/%{rb_ver}/gems/%{mod_full_name}/README.md 
%buildroot/%{_docdir}/%{name}/README.md
 
 %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}/spec

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

Reply via email to