Bug 5200

Summary:	feature wishes for portage
Product:	Portage Development	Reporter:	Hannes Mehnert (RETIRED) <hannes>
Component:	Core	Assignee:	Daniel Robbins (RETIRED) <drobbins>
Status:	RESOLVED INVALID
Severity:	normal
Priority:	High
Version:	2.0
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Hannes Mehnert (RETIRED) gentoo-dev

2002-07-18 14:53:02 UTC

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).

Comment 1 Nicholas Jones (RETIRED) gentoo-dev

2002-07-19 05:23:45 UTC

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