On Sun, 2023-06-25 at 11:19 -0500, Dale wrote: > By default, it has no ruby target it seems, although it used to. The > on/off status changes. Setting to match the old way made it worse, > as > mentioned above. I can't figure out how to make this work. > > Any ideas? Thoughts? > > Dale > > :-) :-) >
Not the same problem I had, but I ran into some "portage wants to do strange things" issues after the Ruby upgrade. A --depclean fixed this up for me by removing ruby30 which was no longer required anywhere. Might give that a go and see if it shakes things out right.
