| 1 |
On Mon, 21 Mar 2022 15:41:14 +0100, hitachi303 wrote: |
| 2 |
|
| 3 |
> >> as far as I understand updating @system first should be safer and |
| 4 |
> >> easier to perform than updating @world directly. It was mention that |
| 5 |
> >> especially after updating the software after a somewhat long period |
| 6 |
> >> this might solve conflicts. I often do experience different and |
| 7 |
> >> wonder what the reason might be. |
| 8 |
> >> |
| 9 |
> >> The example today would work in both ways but @system shows problems |
| 10 |
> >> which @world does not have. Mostly those problems seem to be bigger |
| 11 |
> >> to the point where @system does not work but @world does or manual |
| 12 |
> >> package by package uninstalling and or emerging is required. |
| 13 |
> > |
| 14 |
> > Emerging @world considers the whole dependency tree, so it should give |
| 15 |
> > better results. Emerging @system first is only recommended in cases |
| 16 |
> > where @world fails due to dependency issues, particularly circular |
| 17 |
> > dependencies. |
| 18 |
> |
| 19 |
> That is what I learnd but my experience is that @system has often more |
| 20 |
> dependency issues than @world. |
| 21 |
|
| 22 |
Exactly, which is why @world should be the first attempt, but there are |
| 23 |
times when it fails while @system will succeed. |
| 24 |
|
| 25 |
> Your signature is always a reason to read your emails even when the |
| 26 |
> subject is not appealing. |
| 27 |
> . |
| 28 |
|
| 29 |
:-) |
| 30 |
|
| 31 |
|
| 32 |
-- |
| 33 |
Neil Bothwick |
| 34 |
|
| 35 |
Accordion: a bagpipe with pleats. |
Archives