I currently think on following things concerning portage: -emerge --continue, which continues an emerge which has been aborted (because of power loss,...) I think the code for that is nearly implemented, ebuild foo install checks for this, but didn't work here. -emerge --autoclean=no, to let the configured source in /var/tmp/portage (sometimes You need them).
Both can be accomplished already with ebuild. 1st case: It's a bad idea as you don't know what might be corrupted. You _were_ actively operating on the disk, no? But you can do this anyway: FEATURES="noauto" ebuild /usr/portage/.../blah/blah-0.0.0.ebuild compile 2nd case: You want the final product: FEATURES="noclean" ebuild /usr/portage/.../blah/blah-0.0.0.ebuild qmerge You want the unpacked code: ebuild /usr/portage/.../blah/blah-0.0.0.ebuild unpack
