This adds Ruby 3.4, released yesterday. Release announcements at:

* https://www.ruby-lang.org/en/news/2024/12/25/ruby-3-4-0-released/
* https://www.ruby-lang.org/en/news/2024/12/25/ruby-3-4-1-released/

I'd like to commit this with updates to ruby.port.mk to support the
ruby34 FLAVOR for Ruby ports.

Tested on amd64 since 3.4.0-preview1. New port attached as .tar.gz,
hookup code and ruby.port.mk change inline.  I'll update ruby-module.5
appropriately after commit.

OK to commit?

Thanks,
Jeremy

Index: lang/ruby/Makefile
===================================================================
RCS file: /cvs/ports/lang/ruby/Makefile,v
diff -u -p -u -p -r1.101 Makefile
--- lang/ruby/Makefile	21 Nov 2024 05:53:59 -0000	1.101
+++ lang/ruby/Makefile	27 Dec 2024 01:23:57 -0000
@@ -1,5 +1,6 @@
 SUBDIR =
 SUBDIR += 3.2
 SUBDIR += 3.3
+SUBDIR += 3.4
 
 .include <bsd.port.subdir.mk>
Index: lang/ruby/ruby.port.mk
===================================================================
RCS file: /cvs/ports/lang/ruby/ruby.port.mk,v
diff -u -p -u -p -r1.122 ruby.port.mk
--- lang/ruby/ruby.port.mk	21 Nov 2024 05:53:26 -0000	1.122
+++ lang/ruby/ruby.port.mk	3 Dec 2024 16:46:44 -0000
@@ -25,7 +25,7 @@ MODRUBY_HANDLE_FLAVORS ?= No
 # If ruby.pork.mk should handle FLAVORs, define a separate FLAVOR
 # for each ruby version.
 .    if !defined(FLAVORS)
-FLAVORS=	ruby32 ruby33
+FLAVORS=	ruby32 ruby33 ruby34
 .    endif
 
 # Instead of adding flavors to the end of the package name, we use
@@ -49,11 +49,12 @@ FLAVOR =		ruby33
 
 # Check for conflicting FLAVORs and set MODRUBY_REV appropriately based
 # on the FLAVOR.
-.    for i in ruby32 ruby33
+.    for i in ruby32 ruby33 ruby34
 .      if ${FLAVOR:M$i}
 MODRUBY_REV = ${i:C/ruby([0-9])/\1./}
 .        if ${FLAVOR:N$i:Mruby32} || \
-            ${FLAVOR:N$i:Mruby33}
+            ${FLAVOR:N$i:Mruby33} || \
+            ${FLAVOR:N$i:Mruby34}
 ERRORS += "Fatal: Conflicting flavors used: ${FLAVOR}"
 .        endif
 .      endif

• ruby34.tar.gz (118K)