I was emerging perl the other day. As it was installing (it was done compiling), it seg faulted. That was cleared up, but now it seems that I have to recompile perl all over again. If I try to use `ebuild perl-5.8.7.ebuild install`, it automatically detects that the workdir is full of already compiled binaries. It doesn't touch them. Why can't emerge do this? I was playing around with --resume but don't think I fully understand it. Is --resume what I am looking for? Reproducible: Always Steps to Reproduce:
"If I try to use `ebuild perl-5.8.7.ebuild install`, it automatically detects that the workdir is full of already compiled binaries. It doesn't touch them. Why can't emerge do this?" a) `ebuild .. install` installs stuff, doesn't compile it if it's already there b) you try something with ebuild(1) and then ask why emerge(1) doesn't do it? c) no, --resume will pick up multi-package runs, it won't resume individual packages So, you either want `ebuild ... compile install` or `emerge ...` Or am I misunderstanding something here?
