Dne 16.1.2013 21:18, Bill Nottingham napsal(a):
Jaroslav Reznik (jreznik@xxxxxxxxxx) said:
Yet, it is source level backward compatible with Ruby 1.9.3, so your software
will continue to work.
The updated Ruby also provides better integration with Fedora, especially JRuby.
But not only JRuby, it is also one step closer to be prepared for other
interpreters, such as Rubinius. Provided custom Ruby loader with working name
"rubypick" [1] will allow to easily switch interpreters executing your script,
provides fallback to whatever Ruby interpreter is available on you system, yet
still keeps backward compatibility with all your Ruby scripts.
Reading this, it's source compatible, but not binary compatible, so
everything gets a rebuild? (IOW, akin to many python version updates).
Do you need a side tag for it?
Bill
Yes, everything needs rebuild. It needs rebuild also due to change from
ruby(abi) to ruby(release) we are proposing in guildelines draft and
which was discussed on packaging list (it would need it due to change in
ruby(abi) version anyway).
Yes, we will definitely ask for side tag as soon as FESCo approves this
feature (and hopefully FPC discuss the changes in guidelines). We will
use the tag to build Ruby, all ruby dependent packages and JRuby as well.
Vít
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
