From: Jeremy Evans <jeremy@openbsd.org>
Subject: Re: Ruby 3.2 Removal
To: OpenBSD ports <ports@openbsd.org>
Date: Sat, 1 Nov 2025 22:39:40 -0700

On 11/01 11:56, Marc Espie wrote:
> On Sat, Nov 01, 2025 at 01:32:03PM -0700, Jeremy Evans wrote:
> > Per our standard Ruby support policy, I am planning to remove Ruby 3.2
> > from the ports tree, as it will be completely unsupported before the
> > release of OpenBSD 7.9. Nothing currently depends on it, so
> > this should cause no problems.
> >  
> > Here's the diff for ruby.port.mk. I also have diffs prepared for
> > ruby-module.5 and quirks.
> >  
> > Thanks,
> > Jeremy
> > 
> > Index: ruby.port.mk
> > ===================================================================
> > RCS file: /cvs/ports/lang/ruby/ruby.port.mk,v
> > diff -u -p -u -p -r1.124 ruby.port.mk
> > --- ruby.port.mk	28 Jun 2025 00:36:08 -0000	1.124
> > +++ ruby.port.mk	1 Nov 2025 20:28:02 -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 ruby34
> > +FLAVORS=	ruby33 ruby34
> >  .    endif
> >  
> >  # Instead of adding flavors to the end of the package name, we use
> > @@ -49,11 +49,10 @@ FLAVOR =		ruby34
> >  
> >  # Check for conflicting FLAVORs and set MODRUBY_REV appropriately based
> >  # on the FLAVOR.
> > -.    for i in ruby32 ruby33 ruby34
> > +.    for i in ruby33 ruby34
> >  .      if ${FLAVOR:M$i}
> >  MODRUBY_REV = ${i:C/ruby([0-9])/\1./}
> > -.        if ${FLAVOR:N$i:Mruby32} || \
> > -            ${FLAVOR:N$i:Mruby33} || \
> > +.        if ${FLAVOR:N$i:Mruby33} || \
> >              ${FLAVOR:N$i:Mruby34}
> >  ERRORS += "Fatal: Conflicting flavors used: ${FLAVOR}"
> >  .        endif
> > @@ -153,7 +152,7 @@ SITES?=		${SITE_RUBYGEMS}
> >  EXTRACT_SUFX=	.gem
> >  
> >  .  if ${CONFIGURE_STYLE:L:Mext}
> > -# Use ports-gcc for ruby32 extensions if base does not use clang
> > +# Use ports-gcc for extensions if base does not use clang
> >  COMPILER ?= 	base-clang ports-gcc
> >  COMPILER_LANGS ?= c
> >  # Add build complete file to package so rubygems doesn't complain
> > 
> > 
> I think I would remove the SUBDIRS proper before removing the
> infrastructure support.

The order of operations will be the same as it was for previous Ruby
removals:

* Remove ruby32 support from ruby.port.mk. This is done before the Ruby
  3.2 port is removed, by design.
* Unhook 3.2 from lang/ruby/Makefile.
* Remove lang/ruby/3.2.
* Update quirks.
* Update ruby-module.5.

Do you have a reason why you think we should remove lang/ruby/3.2 before
removing the ruby32 FLAVOR from ruby.port.mk? AFAICT, it would leave the
ports tree temporarily in a state that would allow the ruby32 FLAVOR for
ruby ports, but not build correctly if the ruby32 FLAVOR was used.
Removing the ruby32 FLAVOR from ruby.port.mk first avoids that issue.

Thanks,
Jeremy