On Sat, 19 Mar 2016 19:03:24 +0200 Alan McKinnon <alan.mckin...@gmail.com> wrote:
> On 19/03/2016 18:43, »Q« wrote: > > On Fri, 18 Mar 2016 23:55:19 +0200 > > Alan McKinnon <alan.mckin...@gmail.com> wrote: > > > >> On 18/03/2016 20:43, »Q« wrote: > >>> On Thu, 17 Mar 2016 20:37:04 -0400 > >>> Alec Ten Harmsel <a...@alectenharmsel.com> 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? [big snip] > @module-rebuild is a dynamic set. It translates to "all the packages > you have emerged that install out-of-tree kernel modules" > > So not really a fair comparison. Compare instead against a regular > static set - "a bunch of packages defined by you that go together and > live in /etc/portage/sets/<set_name>" Thanks much for the lesson. I may hijack more of the OP's threads to ask about trivia. :) $ sudo emerge --noreplace @testset Calculating dependencies... done! >>> Recording @testset in "world_sets" favorites file... I had also been under the mistaken impression that --update implied --oneshot, but I see that it's not so.
