| 1 |
On Sat, 19 Mar 2016 19:03:24 +0200 |
| 2 |
Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
| 3 |
|
| 4 |
> On 19/03/2016 18:43, »Q« wrote: |
| 5 |
> > On Fri, 18 Mar 2016 23:55:19 +0200 |
| 6 |
> > Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
| 7 |
> > |
| 8 |
> >> On 18/03/2016 20:43, »Q« wrote: |
| 9 |
> >>> On Thu, 17 Mar 2016 20:37:04 -0400 |
| 10 |
> >>> Alec Ten Harmsel <alec@××××××××××××××.com> wrote: |
| 11 |
> >>> |
| 12 |
> >>>>> emerge --update --newuse --deep --with-bdeps=y system |
| 13 |
> >>>>> --keep-going |
| 14 |
> >>>> |
| 15 |
> >>>> Add "--oneshot", same reasoning as above. |
| 16 |
> >>> |
| 17 |
> >>> When the target is a set (in this case @system), does portage ever |
| 18 |
> >>> add all of it to @world? |
| 19 |
|
| 20 |
[big snip] |
| 21 |
|
| 22 |
> @module-rebuild is a dynamic set. It translates to "all the packages |
| 23 |
> you have emerged that install out-of-tree kernel modules" |
| 24 |
> |
| 25 |
> So not really a fair comparison. Compare instead against a regular |
| 26 |
> static set - "a bunch of packages defined by you that go together and |
| 27 |
> live in /etc/portage/sets/<set_name>" |
| 28 |
|
| 29 |
Thanks much for the lesson. I may hijack more of the OP's threads to |
| 30 |
ask about trivia. :) |
| 31 |
|
| 32 |
$ sudo emerge --noreplace @testset |
| 33 |
Calculating dependencies... done! |
| 34 |
>>> Recording @testset in "world_sets" favorites file... |
| 35 |
|
| 36 |
I had also been under the mistaken impression that --update |
| 37 |
implied --oneshot, but I see that it's not so. |
Archives