Re: Proposed F19 Feature: Ruby 2.0.0 - the latest stable version of Ruby, with major increases in speed and reliability
Dne 16.1.2013 21:18, Bill Nottingham napsal(a): Jaroslav Reznik (jrez...@redhat.com) 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@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Proposed F19 Feature: Ruby 2.0.0 - the latest stable version of Ruby, with major increases in speed and reliability
On Thu, 17 Jan 2013 13:00:33 +0100 Vít Ondruch vondr...@redhat.com wrote: 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. If timing works out could this just be done at the same time as the gcc rebuild? ie, build gcc and then build new ruby, then mass rebuild? kevin signature.asc Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Proposed F19 Feature: Ruby 2.0.0 - the latest stable version of Ruby, with major increases in speed and reliability
Dne 17.1.2013 14:13, Kevin Fenzi napsal(a): On Thu, 17 Jan 2013 13:00:33 +0100 Vít Ondruch vondr...@redhat.com wrote: 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. If timing works out could this just be done at the same time as the gcc rebuild? ie, build gcc and then build new ruby, then mass rebuild? It's a tempting idea, but I would still prefer side tag, since it will allows to do it by our pace, do testing and if something should go really wrong, we could easily revert (i.e. not merge the side tag). Vít -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Proposed F19 Feature: Ruby 2.0.0 - the latest stable version of Ruby, with major increases in speed and reliability
Jaroslav Reznik (jrez...@redhat.com) 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 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
