On Fri, 18 Mar 2016 23:55:19 +0200 Alan McKinnon <[email protected]> wrote:
> On 18/03/2016 20:43, »Q« wrote: > > On Thu, 17 Mar 2016 20:37:04 -0400 > > Alec Ten Harmsel <[email protected]> wrote: > > > >>> emerge --update --newuse --deep --with-bdeps=y system > >>> --keep-going > >> > >> Add "--oneshot", same reasoning as above. > > > > When the target is a set (in this case @system), does portage ever > > add all of it to @world? > > Effectively, yes. That's not what the code does of course (they go > into world_sets) but the behaviour is as if the set was in world, and > gets added/removed as a complete unit Hmm, that doesn't match my experience. I just tested with the smallest set I ever use, @module-rebuild : # emerge @module-rebuild Calculating dependencies... done! >>> Verifying ebuild manifests >>> Emerging (1 of 1) app-emulation/virtualbox-modules-4.3.32::gentoo >>> Installing (1 of 1) app-emulation/virtualbox-modules-4.3.32::gentoo >>> Jobs: 1 of 1 complete Load avg: 2.04, >>> 0.80, 0.52 Auto-cleaning packages... >>> No outdated packages were found on your system. * GNU info directory index is up-to-date. # cat /var/lib/portage/world_sets # file /var/lib/portage/world_sets /var/lib/portage/world_sets: empty I don't think I have anything in make.conf which would change the default behavior WRT world_sets, but here's what I have anyway: FEATURES="binpkg-logs buildsyspkg collision-protect downgrade-backup fail-clean fixlafiles news parallel-fetch parallel-install preserve-libs sandbox strict unknown-features-warn userfetch userpriv usersandbox usersync" EMERGE_DEFAULT_OPTS="--ask-enter-invalid --jobs=8 --load-average 11.2 --with-bdeps y"
