Bug 40814 – Portage feature request: a way for emerge --resume to select which emerge operation is to be resumed

• Product: Portage Development
• Status: VERIFIED LATER

[Description Federico Gherardini 2004-02-08 01:59:47 UTC]

I thimk it would be great to have the possibility to save informations about any emerge operation in some kind of file so that, when you use emerge --resume, you can choose which emerge is to be resumed. This would give the possibility to resume emerge operations besides the last one. I think this would be very useful when an emerge -e world fails and you have to manually emerge some packages to fix the problem. If you do this now you will lose all the informations about the "emerge -e world" and you'll have to restart everything because --resume only resumes the last operation.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

[Comment 1 francesco r 2004-12-05 15:51:41 UTC]

I was thinking at 
emerge --push && make emerge something && emerge --pop --resume
when I've serches for bug cointaining --resume but the idea of save it in a file should be better.
Anyway how portage know what to resume ?

[Comment 2 Jason Stubbs (RETIRED) 2005-07-28 07:25:34 UTC]

Putting a hold on feature requests for portage as they are drowning out the 
bugs. Most of these features should be available in the next major version of 
portage. But for the time being, they are just drowning out the major bugs and 
delaying the next version's progress. 
 
Any bugs that contain patches and any bugs for etc-update or dispatch-conf can 
be reopened. Sorry, I'm just not good enough with bugzilla. ;) 

[Comment 3 Marius Mauch (RETIRED) 2007-01-11 13:01:04 UTC]

Closing as the new --resume handling makes this mostly pointless.

[Comment 4 Zac Medico 2007-01-11 19:49:52 UTC]

See bug #21509, comment #3.