Matt Connell wrote: > 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. > > . >
I seem to recall seeing that somewhere and I ran --depclean after my next update. I don't always run it but I try to run it about once a month, I do updates weekly, generally. I ran it and nothing about ruby in it but it is a good idea to check it. Ruby, python and such can sometimes get weird. Thanks. Dale :-) :-)
