Bug 97440

Summary:	Checking for precompiled data in workdir
Product:	Portage Development	Reporter:	Alex <alex323>
Component:	Core	Assignee:	Portage team <dev-portage>
Status:	RESOLVED INVALID
Severity:	enhancement
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Alex 2005-06-29 20:31:01 UTC

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:

Comment 1 Marius Mauch (RETIRED) gentoo-dev

2005-06-30 04:02:35 UTC

"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?