Ruby 2.6 has received a few patch releases already and should be stable
enough to make the default ruby version. Here's a patch for the switch.
I've updated my process to catch ports that were missed in the switch
from Ruby 2.4 to 2.5.
Tested with a partial bulk of ports that require ruby or any port that
starts with ruby-, both before and after the switch.
Most of these are fairly simple bumps, but there are a few more
devel/ruby-bundler: Drop the bin files from the PLIST on 2.6, as
they as included in ruby 2.6 and conflict with lang/ruby/2.6,-main.
devel/ruby-minitest: Use an empty PLIST on 2.6, as ruby 2.6 includes
x11/kde4/ruby-qt: Add a ruby26 FLAVOR, as one was missing before.
This also requires adding a conflict in the PLIST.
I plan to commit this in a couple days unless I hear objections.
-# Without a FLAVOR, assume the use of ruby 2.5.
+# Without a FLAVOR, assume the use of ruby 2.6.
. if empty(FLAVOR)
-FLAVOR = ruby25
+FLAVOR = ruby26
# Check for conflicting FLAVORs and set MODRUBY_REV appropriately based
@@ -67,8 +67,8 @@ ERRORS += "Fatal: Conflicting flavors us
# The default ruby version to use for non-gem ports. Defaults to ruby
-# 2.5 for consistency with the default ruby25 FLAVOR for gem ports.
+# 2.6 for consistency with the default ruby26 FLAVOR for gem ports.
# Because the jruby FLAVORs use same binary names but in
# different directories, GEM_MAN_SUFFIX is used for the man pages to avoid
RCS file: /cvs/ports/devel/ruby-bundler/Makefile,v
retrieving revision 1.12
diff -u -p -r1.12 Makefile
--- devel/ruby-bundler/Makefile 8 Jun 2017 07:20:51 -0000 1.12
+++ devel/ruby-bundler/Makefile 26 Apr 2019 16:30:49 -0000
@@ -3,6 +3,7 @@
COMMENT= ruby application dependency manager