Date: Wed, 28 Nov 2018 16:09:53 +0000 From: bugzilla-noreply@freebsd.org To: ruby@FreeBSD.org Subject: maintainer-feedback requested: [Bug 233612] Update devel/rubygem-jruby-jars to version 9.2.4.0 Message-ID: <bug-233612-21402-Vc4jZtyDCr@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-233612-21402@https.bugs.freebsd.org/bugzilla/> References: <bug-233612-21402@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
Bugzilla Automation <bugzilla@FreeBSD.org> has asked freebsd-ruby mailing l= ist <ruby@FreeBSD.org> for maintainer-feedback: Bug 233612: Update devel/rubygem-jruby-jars to version 9.2.4.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D233612 --- Description --- I originally had this as part of PR229163, but I am splitting it out becaus= e 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 defa= ult. Furthermore jruby is faster than the regular Ruby and people may want to us= e it on it's own without other ruby versions interfering. jruby ships with jgem which I am using for updating this port but my approa= ch is unelegant as we are still installing the alternative ruby infrastructure= . A clean structure should be devised as all ports that depend jruby (USES =3D = 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-233612-21402-Vc4jZtyDCr>