Re: Proposed F19 Feature: JRuby 1.7 - JRuby is an alternative Ruby implementation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



----- Original Message -----
> On Wed, Jan 16, 2013 at 08:05:23AM -0500, Jaroslav Reznik wrote:
> > 
> > - Changes in packaging
> >  None yet. JRuby will be able to use pure Ruby Gems packaged into
> >  RPM out of
> >  the box, but packaging of Gems with JRuby extensions is turning
> >  out to be
> >  very complicated, so the guidelines for it will be postponed to
> >  next release
> >  (as well as the actual packaging). Users will be still able to
> >  install Gems
> >  with JRuby extensions, both system-wide (into /usr/local/) and
> >  into their
> >  home directories.
> > 
> > [1]
> > https://github.com/bkabrda/jruby.spec/blob/master/rubygems/operating_system.rb
> > [2] https://github.com/bkabrda/rubypick
> >
> As JRuby is setup to share pure ruby gems with ruby, I don't think
> this can
> be approved (inlcuding the update to the jruby package to do this)
> until FPC
> rules on whether it's okay for interpreters and languages which are
> not
> completely compatible to share modules.  FPC will hopefully have
> quorum
> tomorrow morning to meet.  If not, or if they have issues with the
> guidelines, perhaps slavek and I can meet to try to figure out ways
> around
> the issues.  I'll know more after the FPC meeting time tomorrow
> morning.
> 
> -Toshio
> 

(I'm CC'ing Charles Nutter and Thomas Enebo, the main JRuby guys, as hearing their opinions on this would be highly beneficial.)
To explain why we want to share the pure Gems:
In Ruby world, JRuby is using what I would call a "pro-active" attitude. That means that the default assumption is that all the pure Ruby Gems work with JRuby. If not, then someone goes and fixes the stuff. Ruby-SIG is meaning to follow this path (as upstream does). The other approach would obviously be assuming that the Gems don't work and sharing them only if we're 100 % sure that they work completely the same. But we can _never_ be sure of that (there is no way to test that). So to me, it seems that we can either share all pure Ruby Gems and work with upstreams if something breaks (which is not usual, big part of Ruby world is using JRuby without problems these days) or we cannot share anything. I choose the first and I think that's a good step for Fedora to take.

-- 
Regards,
Bohuslav "Slavek" Kabrda.
-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux