| 1 |
On Mon, 21 Feb 2022 22:26:30 +0100, hitachi303 wrote: |
| 2 |
|
| 3 |
> When running an update after a long long time my approach is as follows: |
| 4 |
> |
| 5 |
> emerge -av --depclean <every huge program which will be updated anyway. |
| 6 |
> Stuff like firefox, thunderbird, etc.> |
| 7 |
|
| 8 |
You don't need to unmerge them, just add --exclude "firefox thunderbird |
| 9 |
etc" to your emerge command. |
| 10 |
> |
| 11 |
> emerge -a --depclean --with-bdeps=n |
| 12 |
> |
| 13 |
> only then when there are as few programs installed as possible I run |
| 14 |
> emerge --sync |
| 15 |
> |
| 16 |
> emerge -Dua --reinstall changed-use @world |
| 17 |
|
| 18 |
If it's been a while, it may be easier to update @system first. |
| 19 |
|
| 20 |
> maybe I have to deal with trouble here |
| 21 |
> |
| 22 |
> dispatch-conf |
| 23 |
> |
| 24 |
> emerge -a --depclean --with-bdeps=y |
| 25 |
> --with-bdeps=y shouldn`t do anything |
| 26 |
> |
| 27 |
> revdep-rebuild -i -- --ask |
| 28 |
> |
| 29 |
> glsa-check -t all |
| 30 |
|
| 31 |
You can run this straight after syncing, it may mean you want to update |
| 32 |
affected programs before doing the rest of @world. |
| 33 |
|
| 34 |
> Maybe there is a better way or I've missed some new ways of updating. |
| 35 |
|
| 36 |
|
| 37 |
-- |
| 38 |
Neil Bothwick |
| 39 |
|
| 40 |
Top Oxymorons Number 22: Childproof |
Archives