On Mon, Mar 13, 2017 at 06:43:05PM +0000, Miguel Landaeta wrote: > Package: src:ruby-json > Version: 2.0.1+dfsg-3 > Severity: normal > Tags: patch > > Hi, > > I noticed ruby-json Java extension was not being built from this > package. > > So, since I need that to get JRuby unit tests passing and it should be > useful for real-world users, I added that missing component to this > package. > > If there are no objections to my approach (please see the debdiff > below), I was planning to merge this and do an upload to experimental > very soon. > > This builds OK in sbuild and I'm using it locally to build and test > recent JRuby releases. > > I'm also attaching the build log if anyone is curious about this.
Is this going to be necessary for many packages? If so, we should
probably implement support for JRuby in gem2deb instead.
> +Package: jruby-json
> +Architecture: all
> +Depends: ${misc:Depends},
> + ${shlibs:Depends}
> +Enhances: jruby
> +Description: JSON library for Ruby - java extension
> + This library implements the JSON (JavaScript Object Notation) specification
> in
> + Ruby, allowing the developer to easily convert data between Ruby and JSON.
> You
> + can think of it as a low fat alternative to XML, if you want to store data
> to
> + disk or transmit it over a network rather than use a verbose markup
> language.
> + .
> + This package contains an implementation of JSON Ruby specification written
> in
> + Java and is suitable for use with JRuby interpreter since provides a better
> + performance than the "pure" JSON gem written in Ruby and available in
> ruby-json
> + package.
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.
signature.asc
Description: PGP signature
