1 |
On Mon, Apr 12, 2010 at 12:06 AM, Marc Joliet <marcec@×××.de> wrote: |
2 |
> Am Sun, 11 Apr 2010 17:13:26 -0700 |
3 |
> schrieb Mark Knecht <markknecht@×××××.com>: |
4 |
> |
5 |
>> On Sun, Apr 11, 2010 at 5:00 PM, Neil Bothwick <neil@××××××××××.uk> wrote: |
6 |
>> > On Sun, 11 Apr 2010 16:11:53 -0700, Mark Knecht wrote: |
7 |
>> > |
8 |
>> >> > Doing system first makes good sense. Then you can update your config |
9 |
>> >> > files, follow the openrc update etc and then reboot. The world part of |
10 |
>> >> > the update will take quite a while, especially if you use KDE or |
11 |
>> >> > GNOME. |
12 |
>> >> |
13 |
>> >> <hehe> Less than most PC. It's an i7-980x with 24GB of RAM with RAID1. |
14 |
>> > |
15 |
> |
16 |
> Gah, I'm getting PC envy ;-) ! |
17 |
> |
18 |
>> A couple of packages in this OpenRC upgrade aren't building. I hope |
19 |
>> they are less important. So far groff and help2man have failed so I |
20 |
>> did --resume --skip-first and moved on for now. |
21 |
> |
22 |
> Just a note: you can also specify "--keep-going" and portage will do that for |
23 |
> you and even recalculate the dependencies before continuing. After it's done, |
24 |
> it gives you a message listing the packages that failed. |
25 |
> |
26 |
|
27 |
Thanks for pointing that out. When doing a long set it means I don't |
28 |
have to keep coming in here to make sure it's doing the most it can. |
29 |
Nice addition. |
30 |
|
31 |
Cheers, |
32 |
Mark |