On 3/8/21 4:16 PM, Neil Bothwick wrote:
It would have to be done before the first update, when the repo was
set to a date just after the last update.
Yes and no.
It really could have been done at any point along the way.
Also, with the git version of the portage repo, I could switch back to
the branch from any time I wanted to.
You can rephrase that as "I left it at the default", which is an
acceptable answer :)
*nod*
It means you probably spent a lot of time compile gcc versions only
to carry on using the old version, but as you said, this wasn't about
efficiency.
Wouldn't the next execution of gcc, post Emerge & Installation use the
newly emerged binary?
If not next package in a given emerge run didn't use the new gcc, I
would fully expect that subsequent emerges would use the new gcc.
You were going to emerge -e @world at the end anyway, which would
get everything built with the latest toolchain.
Yes.
I have initiated a full system backup. I'll start an `emerge -e @world`
after that finishes.
I'll actually do the full suite:
1) emerge -e @world
2) emerge --depclean --verbose n
3) emerge @preserved-rebuild
4) revdep-rebuild
I expect that #3 should be a NoOp and just burn CPU cycles.
I don't know anything else that can be done to make a Gentoo box happier
(from a software standpoint).
Most of the effort for you was developing the procedure. All the real
effort was left to the computer.
Exactly!
Well, developing the method /and/ establishing trust therein.
I was thinking of a week max.
I suspect that would be quite safe.
--
Grant. . . .
unix || die
