On Fri, Jun 12, 2020 at 2:40 AM n952162 <[email protected]> wrote: > > Presumably, 13.0, unless some process had already made the 13.0 -> 17.0 > jump without my knowledge.
Ok, you're in fairly uncharted waters. The impact is mainly to gcc so if you haven't updated that then most likely nothing is broken yet, and you can probably update portage safely because it doesn't use gcc. However, you probably should rebuild libtool and then the toolchain after switching to a newer gcc. > > Well, yes, but it's really pretty onerous. If you have gentoo in > embedded systems, you've got to spend considerable administrative effort > in each one just maintaining the status quo. > > I mean, there's no competition to gentoo, of course. But a design goal > could be to have a one-step sync, of some sort. In such a situation you're probably better off managing that system more like a docker container. Build the entire image off-host from scratch instead of trying to upgrade it in place, and just migrate whatever data you have. You can still use Gentoo so that everything is tailored/etc, but you'd be generating a completely new image from scratch and just flashing it, vs trying to do updates on an embedded system. You really can't reliably do infrequent in-place updates on Gentoo systems. Sure, you can go a few months between updates, but the 17.0 profile came out in 2017... -- Rich
