On 2025-12-19, EssenSea wrote: > 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.
Perhaps you can add "--with-bdeps n" or "--with-bdeps y" where preferred to achieve that consistency, or at least get closer to it? Quoting the online manual page for emerge(1): > Since many users of binary packages do not want unnecessary build time > dependencies installed, this option is not automatically enabled for > installation actions when the --usepkg option is enabled. In order to > pull in build time dependencies for binary packages with --usepkg, > --with-bdeps=y must be specified explicitly. This also applies to op‐ > tions that enable the --usepkg option implicitly, such as --getbinpkg. On 2025-12-19, EssenSea wrote: (cont'd) > 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. > > > -- Nuno Silva
