On 2/24/21 9:29 PM, Grant Taylor wrote:
I'm currently doing an "emerge -DUNe @system" on the restore of
/usr/portage (typical PORTDIR) from prior to messing with things today.
The system is now stable with a full -DUNe @system.
emerge -DUNe @system
reboot
emerge -DUNe @world && emerge --depclean --verbose n && revdep-rebuild
I've got multiple GB of git data. It looks like there are ~568 thousand
commits between March 24th last year and now. Once that's good, and I'm
back at a stable place, I'll try changing PORTDIR to be the git repo and
telling git to switch to the commit that's from March 25th. Then I'll
see if anything needs to be updated, doing so as necessary. Then I'll
leap frog a week at a time seeing what needs to be updated, doing so as
necessary. /Hopefully/ I can slowly walk forward. Time will tell.
I was able to extract the last commit for every day between now and
2020-03-24 and make a branch for it.
10 have git switch to the next day
20 emerge -aDUN @world
30 assess / deal with masked packages
40 goto 10
It /looks/ like things are working.
Yes, emerge is spending a LOT of time mulling over things. Many days
have been "Nothing to merge; quitting."
If I can slowly make my way forward in time via git commit points, I
/think/ that I /should/ be able to deal with profile and / or compiler
and / or glibc changes just like I would have X number of months ago. I
/think/!
One added advantage of doing this day by day is that when I do get to
the big changes, things should be fairly clean. Thus hopefully
simplifying the big changes.
--
Grant. . . .
unix || die
