| 1 |
On Monday, 20 September 2021 15:52:03 BST Gerrit Kuehn wrote: |
| 2 |
> On Mon, 20 Sep 2021 15:29:30 +0100 |
| 3 |
> |
| 4 |
> Michael <confabulate@××××××××.com> wrote: |
| 5 |
> > Personally, I'd back up /home /etc and world file, plus any databases |
| 6 |
> > or websites if stored under /var/, then untar the latest stage 3 |
| 7 |
> > tarball and update @system and @world. |
| 8 |
> |
| 9 |
> Just extracting stage3 over everything that is already there? |
| 10 |
|
| 11 |
No, I move out of the way the config/data files I want to keep and move them |
| 12 |
back in after untarring the stage 3. |
| 13 |
|
| 14 |
|
| 15 |
> > Overall it should be a *much* |
| 16 |
> > faster approach to allow you to bring your installation up to date. |
| 17 |
> |
| 18 |
> Well, yeah, your mileage may vary. |
| 19 |
|
| 20 |
Quite, if you can get your existing installation to only run a minimal number |
| 21 |
of rebuilds to arrive at an upgraded toolchain, then the benefit of |
| 22 |
reinstalling wouldn't be there. This could have been the case on an average |
| 23 |
year, when python deprecations didn't accelerate and EAPI didn't change. If |
| 24 |
however you end up tying up yourself in knots with subsequent python upgrades |
| 25 |
and difficult to resolve conflicts, then the pain Vs gain calculus changes. |
Archives