On Sat, Nov 01, 2025 at 10:39:40PM -0700, Jeremy Evans wrote:
> On 11/01 11:56, Marc Espie wrote:
[...]
> > 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.

I suspect Marc assumed that "SUBDIRS += ruby-foo,ruby32" were all
still around the place.  If some still existed then yes, it would be
better to start with dropping them.  But (as usual) you have already
unhooked the ruby32 packages:

  revision 1.2492
  date: 2025/05/15 01:33:18;  author: jeremy;  state: Exp;  lines: +0 -10;  commitid: P9D1e43IZFyCGGWb;
  Stop building ruby32 ports by default
  
  Ruby 3.2 is now in security maintenance mode, so per our Ruby support
  policy, we will no longer build ruby32 packages by default.

HTH,
-- 
jca