On Tuesday 05 March 2013 6:11:53 pm Jeremy Evans wrote: > This updates to the latest version of JRuby, 1.7.3. The JRuby 1.7 > series was first released last October, but due to pthread issues > not fixed until after ports lock, we were not able to update to it > as it caused JRuby to segfault far more often than before. > > With the pthread fix, JRuby 1.7 runs fine. Here's the highlights: > > * 1.9.3 is now our default runtime mode (--1.8 is available) > * Ruby standard library updated to 1.9.3p327 > * Many 1.9.x compatibility fixes > * Support for invokedynamic > * Performance and concurrency improvements throughout > * All known 1.9 encoding issues resolved > * Kernel#exec now does a true native exec on all platforms > * Improvements and fixes to Java integration and embedding > * Native features now better supported on OpenBSD > * Update to Rubygems 1.8.24 > * Update to Rake 0.9.2.2 > * A few ruby security issues fixed > > Here are the ports changes: > > * C extension support is no longer included. It was always > considered experimental, was not supported in 1.9 mode, > and never ran perfectly on OpenBSD. > > * jruby.jar is now used instead of jruby-complete.jar. This > shouldn't have a significant external effect, but makes the > OpenBSD package more similar to packages on other OSes. > > * A hack were used to attempt to ensure that this doesn't > break existing installations. The gem installation directory > has changed upstream, but we link the new directory to the old > directory so that you don't lose gems previously installed. > > Tested on amd64 and i386. Looking for OKs to commit after ports > fully unlocks.
Glancing at the diff and it looks reasonable to me. > @@ -31,14 +29,15 @@ MODJAVA_VER = 1.7+ I noted that you have marked the port as 1.7+ but this page https://github.com/jruby/jruby indicates it is 1.6+. Please consider using 1.6+ for additional flexibility for users to chose which jdk to run it with. I will take a closer look at it soon. Regards, -Kurt
