emerge -e world will pick up nearly all packages emerge --resume to pick where a package fails.
It works fine on a small, simple systems but fails more often than not on complex desktops because there always seem to be a few packages that need some work before they will build. I usually trap the output of emerge -e world to a file, manually edit it so each line becomes "emerge package && \". The advantage is that when it fails, you can just comment out/delete the done packages and pickup where you left off. --resume is very flakey, often coming back with "nothing to do" and wanting to start from the beginning again (and I have over 600 packages on this machine!), and if you do an emerge when trying to fault find a failing package, --resume wipes its memory of where it was up to - semi-useless! World misses some packages as only primary packages are recorded, many deps are not included - in most cases this is not critical/ Lastly, there are some scripts out there to handle this process for you in a better fashion than "-e", but they regularly break as portage evolves, so you might try searching the forums or someone may post one that works. On the fly is the way to go: think how much time you have invested in tuning your current system that will mostly be lost. The machine will still be usable during the recompile, unlike a wipe/reinstall. Have fun! BillK On Sun, 2004-01-04 at 06:40, Michael Balamuth wrote: > Hi All, > > I'm trying to understand the underlying specifics of installing Gentoo > versus changing it on the fly. Since optimization and tailoring is the goal > of the philosophy behind the install of Gentoo, would the same thing be > accomplished on a running system by setting new USE flags and doing: > > emerge system (not update) followed by emerge world (again not update) -- [EMAIL PROTECTED] mailing list
