On Tue, Mar 14, 2017 at 07:33:22AM -0300, Antonio Terceiro wrote: > > Is this going to be necessary for many packages? If so, we should > probably implement support for JRuby in gem2deb instead.
I don't think this is going to be necessary for many packages. From the top of my head I can only think about 3 or 4 popular gems that provide a Java extension: ruby-json, ruby-psych, nokogiri and jruby-openssl. Of course there are a few more out there, but I believe those are the most used anyway. - jruby-openssl is clearly tied to JRuby and is already packaged. - ruby-psych (in the pipeline, ITP: #809469). - nokogiri (I'm not aware of any plan to work on this currently). - ruby-json (being discussed in this bug report). It would be nice to have more support for jruby in gem2deb but at the moment it works OK. > At the moment we handle all supported Ruby interpreters on a single package, > but that is only for multiple versions of MRI when we have them > simultaneously. > I'm not sure we want a new binary package, specially if this is going to be > needed for many packages. I see, I'm also not sure a new binary package is needed. If I keep everything on the current package, my change only adds two small jar files under /usr/lib/ruby/vendor_ruby/json/ext directory and this works perfectly with jruby as is. So, I think this is even a better approach, so thanks for the clarification. If there are no more objections, I'll keep everything in ruby-json. Thanks, Miguel. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. "Faith means not wanting to know what is true." -- Nietzsche
signature.asc
Description: Digital signature
_______________________________________________ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
