It would be very nice if emerge --resume actually checked to see if an emerge of a package had been started and tried to pick up the make where it had left off, rather than re-extracting and re-configuring everything. That way, one could interrupt long builds (such as kdelibs, which took more than three hours on my machine) and resume them later. Bearing in mind that emerge --resume is not guaranteed to succeed anyway, it could try reemerging the package from start if that failed. Reproducible: Always Steps to Reproduce: 1. 2. 3.
> rather than re-extracting and re-configuring everything. FYI, `env FEATURES=keepwork emerge --resume` has almost the same behavior, except the workdir is not cleaned after successful install. Unfortunately, there is not a separate src_configure() phase, so something like confcache is currently needed in order to avoid complete re-configuring. > emerge --resume is not guaranteed to succeed anyway, it could try reemerging the package from start if that failed. Perhaps your proposed feature should be implemented in FEATURES, like keepwork, and that way when it fails you can run `emerge --resume` with that feature disabled.
Not a good idea, might result in corrupted packages (not the same as failed packages). Use the ebuild(1) tool for such "low-level" things.
