Issue #6590 has been updated by vo.x (Vit Ondruch).


kosaki (Motohiro KOSAKI) wrote:
>  Actually, this is not bigdecimal issue. It is gem discovery issue. MRI
>  support two extension types,
>  C and Ruby. JRuby also support two extension types, Java and Ruby. gem
>  loader should realized
>  the fact and prefer to look up Java implementation when used from
>  JRuby. I think.

Actually that is exactly what RubyGems do and what Aaron is proposing. Take nokogiri [1] for example. If you are using MRI, then the nokogiri gem is taken. If it happens you are windows user, then RubyGems downloads nokogiri-x86-mingw32 and if you are JRuby user, then the nokogiri-java version is prefered. They are all just nokogiris, so RubyGems takes the gems from one location. So the MRI gem will be uploaded by mkrn and the JRuby version by headius. It should be just somehow synchronized when new gem version is released.


[1] https://rubygems.org/gems/nokogiri


----------------------------------------
Feature #6590:  Dealing with bigdecimal, etc gems in JRuby
https://bugs.ruby-lang.org/issues/6590#change-27742

Author: headius (Charles Nutter)
Status: Open
Priority: Normal
Assignee: nahi (Hiroshi Nakamura)
Category: 
Target version: 


 Hello!
 
 http://jira.codehaus.org/browse/JRUBY-6704
 
 We have a need to make the "bigdecimal" gem work for JRuby, so that
 distros (like Red Hat, mentioned in the above bug) and users can have
 the same gemspec for JRuby with updated bigdecimal gem references.
 
 I'm not sure the best way to proceed.
 
 The bigdecimal source and gemspec all come from MRI source, and are
 not versioned separately. That means we can't simply share a
 repository for the JRuby bits. We could maintain a forked version in
 our forked "jruby/ruby" repository, but that wouldn't be part of the
 bigdecimal release cycle then.
 
 So I'm looking to you for guidance.
 
 The BigDecimal lib is here in JRuby:
 https://github.com/jruby/jruby/tree/master/src/org/jruby/ext/bigdecimal
 
 It might be simplest if for now there's a dummy "bigdecimal" gem
 pushed for JRuby that does not contain anything, since we would have
 other complications if we tried to remove BigDecimal from JRuby proper
 (it is referenced elsewhere int eh code, etc).
 
 Thoughts?
 
 - Charlie


-- 
http://bugs.ruby-lang.org/