https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233612
Bug ID: 233612
Summary: Update devel/rubygem-jruby-jars to version 9.2.4.0
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: Individual Port(s)
Assignee: r...@freebsd.org
Reporter: p...@freebsd.org
Flags: maintainer-feedback?(r...@freebsd.org)
Assignee: r...@freebsd.org
Created attachment 199642
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=199642&action=edit
Update jruby-jars and use jgem
I originally had this as part of PR229163, but I am splitting it out because I
think it points out a structural problem:
Ports depending on jruby should not depend at all on installing the native ruby
as they are generally incompatible: Newer jruby is compatible with ruby 2.5,
older jruby is compatible with ruby 2.3. We currently ship Ruby 2.4 as default.
Furthermore jruby is faster than the regular Ruby and people may want to use it
on it's own without other ruby versions interfering.
jruby ships with jgem which I am using for updating this port but my approach
is unelegant as we are still installing the alternative ruby infrastructure. A
clean structure should be devised as all ports that depend jruby (USES = jruby
?) are affected:
databases/rubygem-activerecord-jdbc-adapter
databases/rubygem-activerecord-jdbcmysql-adapter
databases/rubygem-jdbc-mysql
devel/rubygem-warbler
sysutils/puppetserver6
www/rubygem-jruby-rack
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-ruby@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ruby
To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
