Hello community,

here is the log from the commit of package rubygem-pry for openSUSE:Factory 
checked in at 2013-05-27 10:00:44
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/rubygem-pry (Old)
 and      /work/SRC/openSUSE:Factory/.rubygem-pry.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "rubygem-pry"

Changes:
--------
--- /work/SRC/openSUSE:Factory/rubygem-pry/rubygem-pry.changes  2013-05-02 
11:47:35.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.rubygem-pry.new/rubygem-pry.changes     
2013-05-27 10:00:45.000000000 +0200
@@ -1,0 +2,6 @@
+Mon May 13 07:35:19 UTC 2013 - [email protected]
+
+- updated to version 0.9.12.2
+ * reload-code (with no args) should reload 'current file', issue #920 
+
+-------------------------------------------------------------------

Old:
----
  pry-0.9.12.1.gem

New:
----
  pry-0.9.12.2.gem

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

Other differences:
------------------
++++++ rubygem-pry.spec ++++++
--- /var/tmp/diff_new_pack.yklvrv/_old  2013-05-27 10:00:46.000000000 +0200
+++ /var/tmp/diff_new_pack.yklvrv/_new  2013-05-27 10:00:46.000000000 +0200
@@ -17,7 +17,7 @@
 
 
 Name:           rubygem-pry
-Version:        0.9.12.1
+Version:        0.9.12.2
 Release:        0
 %define mod_name pry
 %define mod_full_name %{mod_name}-%{version}
@@ -60,6 +60,8 @@
 %gem_install -f
 mv %{buildroot}%{_bindir}/pry{,%{mod_branch}}
 ln -s pry%{mod_branch} %{buildroot}%{_bindir}/pry
+mkdir -p %{buildroot}%{_docdir}/%{name}
+ln -s %{_libdir}/ruby/gems/%{rb_ver}/gems/%{mod_full_name}/LICENSE 
%buildroot/%{_docdir}/%{name}/LICENSE
 
 # MANUAL
 rm -rf %{buildroot}%{_libdir}/ruby/gems/%{rb_ver}/doc/%{mod_full_name}/
@@ -75,6 +77,7 @@
 
 %files
 %defattr(-,root,root,-)
+%{_docdir}/%{name}
 %{_bindir}/pry%{mod_branch}
 %ghost %{_bindir}/pry
 %{_libdir}/ruby/gems/%{rb_ver}/cache/%{mod_full_name}.gem

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

Reply via email to