#5463: Koji tag for Ruby 2.0.0 / JRuby 1.7

[Vít Ondruch]

Dne 21.2.2013 11:16, Bohuslav Kabrda napsal(a):
> ----- Original Message -----
>> On 02/21, Bohuslav Kabrda wrote:
>>> ----- Original Message -----
>>>> Vít Ondruch wrote, at 02/21/2013 01:03 AM +9:00:
>>>>> Hi everybody,
>>>>>
>>>>> We obtained side tag for Ruby 2.0.0 rebuild. So these are steps
>>>>> which will follow:
>>>>>
>>>>> 1) Build rubypick
>>>>> 2) Merge my ruby-2.0 branch into master, update to the latest
>>>>> revision available in ruby_2_0_0 branch. I would like to ask
>>>>> you
>>>>> for a review of the spec. There are not all patches, namely the
>>>>> webrick test suite failure [1] (on the other hand, I did not
>>>>> met
>>>>> this issue recently).
>>>>> 3) Bootstrap RSpec
>>>>> 4) Bootstrap other test frameworks
>>>>> 5) Build all other libraries.
>>>> Also, while
>>>> https://fedoraproject.org/wiki/Features/Ruby_2.0.0
>>>> says "Requires rebuilding numerous packages that depend on ruby.
>>>> All these packages have to be updated to support new virtual
>>>> provides.",
>>>> the following page
>>>> https://github.com/jruby/jruby/wiki/C-Extension-Alternatives
>>>> says jruby does not support C extensions at all and lots of
>>>> rubygems packages and ruby-based GUI programs contain / use
>>>> C extensions. Would you make it clear how to package these?
>>> Packaging these for MRI will stay the way it is (except for the
>>> general change in requiring ruby(release) instead of ruby(abi)).
>>> Packaging for JRuby hasn't been sorted out yet completely, but here
>>> are the most important points:
>>> - I don't consider packaging C extensions for JRuby supportable, so
>>> libraries with C extensions shouldn't be packaged for JRuby at
>>> all.
>> What about gems like nokogiri that ships both C and Java extensions?
>>
> That relates to the third point. There will definitely be rules for packaging them, but not in F19, unfortunately. After some discussions with Vit, we have decided that we need better understanding of extension gems for both implementations and so we would like to take some more time to do things properly.

As a workaround, you should be able to install nokogiri locally, using 
'jgem install nokogiri' or 'gem _jruby_ install'.

Actually we deferred this topic for next release, because there are 
multiple cases, such as:

* gem with c and jruby extensions
* only jruby gem

Which creates some weird scenarios and RPM/YUM are not capable enough to 
do everything right without compromises :/


Vít