Viorel Munteanu <[email protected]> writes:

> La 18.12.2025 18:29, EssenSea a scris:
>> Here's my question, I've noticed that 'emerge -avuUD @world' and 'emerge
>> -avguDU @world' will result in some differences, normal, 'guUD' will
>> result in less pkgs to be updated. And after 'guDU' finished, if I run
>> 'uDU', seems still some pkgs need to be updated. I'm not sure why this
>> is. Is someone familiar with this?
>
> Since -g installs binary packages, it may skip some dependencies that are only
> required at build time.  Probably that's what causes your differences.
>

Thanks for your reply.

If this is the reason of the differences, I'm afraid to consider that
-uDU is not consistent fullly enough with binary pkgs which were already
been installed. Since -uDU after -guDU will cause those building time
dependencies be required again, and which seems unnessary.

And if that's so, the upgrade way will be spilt up into two way, either
upgrade with binary pkgs sustained and consistent, or only use
irresistible binary such as gcc and dist-kernel-bin and even do not use
binary for consistent if the hardware are good enough for building
everything locally.


Reply via email to