> 1) How do I recover from a failed build without emerge starting again > from the tarball extraction? In this case, kdeaddons takes 2 hours to > get to the failure.
Check out ccache - it won't work like a download resumer, but by caching compiled files it will speed you up signifigantly. As I remember (been a long time since I've set it up!), just just need to emerge it, and maybe set a cache limit via either /etc/make.conf or directly with /usr/bin/ccache/ccache. > 2) How do I package a build to install on another gentoo machine? Assuming you want the same architecture/cflags/useflags, just emerge with the option --build-pkg. That will tar.bz2-up everything into a file in /usr/portage/packages. To emerge on another system, just transfer that file to another machine's package directory and use the emerge flag --use-pkg. > 3) Is there a built-in mechanism to script the installation? I don't > mind having the machine run for hours at a time; it's the constant need > to check on it then start the next emerge that's aggravating. You can string together multiple arguments in emerge - for example, 'emerge gnome evolution galeon' will emerge gnome and its dependencies, then evolution and its dependencies, and finally galeon and its dependencies. Do a 'man emerge' or 'emerge --help' for more information, and check out the portage manual at http://www.gentoo.org/doc/en/portage-manual.xml I'm guessing your next question will have to do with config files, so play with 'etc-update' sometime. -- Alec Berryman <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part
