Not something I take lightly, nor is it something I look forward to doing. In Gentoo the emerge “-e” means rebuild all packages installed on the system that portage has recorded. A quick ‘equery -l “*”‘ will list all packages installed.
So why do I do this every year or so? Just to make sure I have not messed something up over time. It is not something I look forward to because the time from start to finish is measured not in hours, but days. For example, it took my i7 laptop (1,400+) packages with SSDs and plenty of ram 24+ hours to finish. However, in the end I was confident the system was in good shape.
So here are my tips at making this painful experience a little less painful.
1. I start by getting the system in the best shape possible:
emerge -v –update –deep –newuse –with-bdeps=y –autounmask-write @world
If you are paranoid careful then do:
2. Next: cd /var/log/portage/elog
You should find the file summary.log. Rename it or delete it, whatever suites you. Once the big emerge starts, all the messages will be logged to a new summary.log file.
2. Execute: emerge -pve –keep-going @world
Note the “p” for pretend. If everything is good then it should tell you that the Oracle Java packages need to be downloaded. This is a good time to download them (I have Jre and jdk packages installed), move them to portage/distfiles, and do not forget:
chown portage:portage <file>
to the files. Make a mental note of the total number of packages to build.
3. Start by executing: emerge -ve –keep-going @world
Why the keep-going? Because if everything is good after step 1 then any issues should be minor and this keeps from having to start the process from the beginning.
Now all there is to do is wait and hope for the best which usually does not help. As the emerge progresses with each new package the typical package number X of Y (total) being processed. So if you start with a total of 1,400 packages and later notice emerge outputting 20 of 800 then there has been a problem which has been skipped (note: the –keep-going option). Go check the summary.log file to find what the problem might have been. The best part is that you should be able to fix it while the emerge -e keeps churning along.