On Sat, 01 May 2010, Caleb Maclennan wrote:
2010/5/1 caleb ca...@pld-linux.org:
- patched setup script to run on ruby-1.9
+Patch0: %{name}-ruby19.patch
+%patch0 -p1
Some [widely bemoaned] changes to the way ruby handles string encoding
from 1.8 to 1.9 require changes in
2010/5/1 caleb ca...@pld-linux.org:
- patched setup script to run on ruby-1.9
+Patch0: %{name}-ruby19.patch
+%patch0 -p1
Some [widely bemoaned] changes to the way ruby handles string encoding
from 1.8 to 1.9 require changes in some scripts to run reliably. I
took a cue from
On Sat, 01 May 2010, Caleb Maclennan wrote:
2010/5/1 caleb ca...@pld-linux.org:
- patched setup script to run on ruby-1.9
+Patch0: %{name}-ruby19.patch
+%patch0 -p1
Some [widely bemoaned] changes to the way ruby handles string encoding
from 1.8 to 1.9 require changes in
On 1 May 2010 06:58, Caleb Maclennan ca...@pld-linux.org wrote:
However this breaks the package build on ruby 1.8 systems. Is there an
acceptable way to mark a patch in the spec for inclusion only if the
host system is running a certain version of a package?
Writing portable patches is the
2010/5/1 Radosław Zieliński rade...@gmail.com:
[...]
if RUBY_VERSION 1.9
Oops: this should have been =, instead of .
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en