Hi,
I am currently the maintainer of Maven and ~100 Java packages in Fedora
so I can offer my view.
We are currently maintaining Maven with all its dependencies all built
from source, which is the reason for having so many dependencies. Java
packages may not ship binary JARs or .class files.
I see JRuby is half-written in Java and uses Maven for build so I can
also offer my help with packaging and discovering its dependencies.
On 12. 5. 2026 19:59, Charles Oliver Nutter wrote:
On Tue, May 12, 2026 at 12:43 PM Fabio Valentini
<[email protected]> wrote:
I think just "unpacking a tarball" won't be appropriate for an
official package, assuming that this includes pre-built JAR files?
Those would all need to get built from source during the package
build, but this should be a solveable problem. More concrete feedback
will probably happen once you can share a working package / RPM spec
file and / or submit that for package review.
Oh sure, I understand that. I just provide the example of "unpacking"
to show that there's not much as far as native dependencies required
once a JDK is available.
JRuby itself is published to Maven, of course, but the "dist" package
most people install is distributed as a a tarball or zip containing:
* pre-built jar(s) for JRuby itself
* a set of bin scripts to launch JRuby and provided tools
* a whole bunch of Ruby sources and additional jar files to provide
the Ruby standard library (most of the pure-Ruby is the same code as
in standard Ruby).
We also publish the entire dist to Maven:
https://central.sonatype.com/artifact/org.jruby/jruby-dist. The main
jar file we ship is largely equivalent to the `jruby-core` Maven
artifact, with all third-party JVM libraries bundled into the same file.
I'm not sure how finely the JRuby dist would need to be sliced up to
become an acceptable Fedora package. Looking at standard Ruby packages
from https://packages.fedoraproject.org/pkgs/ruby/ it doesn't appear
that each individual standard library is split off into its own
package, and there's some aggregate packages for "bundled"
(preinstalled) and "default" (in stdlib but upgradable) gems. JRuby
has the same basic split and roughly the same layout of how we ship
the standard library.
Perhaps someone who maintains the existing Ruby packages could help me
figure out what needs to change to support the same packages for JRuby?
--
Marián Konček
--
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it:
https://forge.fedoraproject.org/infra/tickets/issues/new
