I like it, but I'm not sure I'd agree with the --keep-going on the world update. I've seen that cause a few problems that would have been easier to handle if the emerge had died at the first sign of trouble.

On a different note, is a full system upgrade the process of checking everything for updates? If so, then you need to add at least an:

Code:

emerge -DuvaN system

Otherwise you can also consider rebuilding the entire set (Due to modifications to gcc or another piece of the toolchain) via:

Code:

emerge -ave system && emerge -ave system && emerge -ave world

That last one isn't really an upgrade, but it might be appropriate to mention it and when it's applicable.

1) Sometimes depclean should be run twice: before and after revdep-rebuild.
2) You missed very important step between 2 and 3: fix dozen of compilation/install failures .
3) lafixer is often needed during world update due to failed packages because some "useless" *.la file was removed from the system._________________Per aspera ad astra!

If it crash, I want to see it actually, so --keep-going is maybe not a good idea for someone who is new to Gentoo._________________Sysadmin of GentooQuébec.org Wiki Signature
IRC on Freenode : #gentoo-quebec

If it crash, I want to see it actually, so --keep-going is maybe not a good idea for someone who is new to Gentoo.

I think "--keep-going" is very good most times. When I wake up, I don't want to see a world update has interrupted at the beginning, because Frozen-Bubble failed to emerge. If an important package fails, mostly it and some depended packages fails and nothing more. It is very very rare that something bad can happen. I am using it since it is available. Nothing wrong has gone with it. Also at the end, portage gives a list of failed emerges.
My update way:

If it crash, I want to see it actually, so --keep-going is maybe not a good idea for someone who is new to Gentoo.

This is very good command indeed, it saved several days of my life.

When you performing large updage (e.g. 2100+ packages installed and update once per two months) on ~arch, some packages will definitely cease to compile. Usually I have one failure per 50-100 packages being updated.

Without --keep-going option update will stop after each error, and I personally can't monitor it 24/7, but only at evenings or spare time on weekends. Thus huge amount of time and my nerves will be lost due to near dozen of such breaks. With --keep-going option you can see in the end what dies, you can always read build logs in /var/tmp/portage/ and decide what action should be done to fix the problem. --keep-going way approach requires one/two time manual intervention in the build process, which saves both time and health.

And one additional point should be emphasized: always read emerge output, even if this takes several dozens of screens. Some notes are almost critical for normal further performance: e.g. you must rebuild all x11-drivers installed (even if they are not updated) if Xorg was updated from x0.y0.z0 to x1.y1.z1, where x or y changed; otherwise you will encounter very unpleasant situation when both keyboard and mouse cease to work after X upgrade._________________Per aspera ad astra!

And one additional point should be emphasized: always read emerge output, even if this takes several dozens of screens. Some notes are almost critical for normal further performance: e.g. you must rebuild all x11-drivers installed (even if they are not updated) if Xorg was updated from x0.y0.z0 to x1.y1.z1, where x or y changed; otherwise you will encounter very unpleasant situation when both keyboard and mouse cease to work after X upgrade.

Without --keep-going option update will stop after each error, and I personally can't monitor it 24/7, but only at evenings or spare time on weekends. Thus huge amount of time and my nerves will be lost due to near dozen of such breaks. With --keep-going option you can see in the end what dies, you can always read build logs in /var/tmp/portage/ and decide what action should be done to fix the problem. --keep-going way approach requires one/two time manual intervention in the build process, which saves both time and health.

Agreed. To me this is a huge time saver. Before that I had to use external scripts for this. On most machines (even at work) I make that default with

Code:

EMERGE_DEFAULT_OPTS="--keep-going --jobs 6"

in my /etc/make.conf

and use emerge --ignore to disable that on the rare occasion that I do not want it to keep going.

I do adjust the jobs param for lesser powered systems to 2. This is a quad core._________________John

As for the "recipe" consider update. It does all the above, and @preserved-rebuild etc when required, as well as a whole lot more. You can configure practically everything, and it's designed for use in scripts as well as interactively.