Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 68694 - Patch to emerge to show status of "portage cache update" in percents.
Summary: Patch to emerge to show status of "portage cache update" in percents.
Status: RESOLVED FIXED
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Enhancement/Feature Requests (show other bugs)
Hardware: All Linux
: High enhancement (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords: InVCS
Depends on:
Blocks:
 
Reported: 2004-10-24 05:30 UTC by Riku Palomäki
Modified: 2005-07-14 06:58 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
The patch for emerge (emerge.patch,897 bytes, patch)
2004-10-24 05:31 UTC, Riku Palomäki
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Riku Palomäki 2004-10-24 05:30:49 UTC
I hated that "Updating Portage cache..." -thing, because it didn't show how much there was things to do. This simple patch makes emerge to show current position of cache update in percent, for example:
>>> Updating Portage cache:   22%

I have never coded with python before, so I think this is not ready feature. Some comments are welcome.
I don't know does this slow things down on a old computer, with my computer it really makes no difference in time.

Reproducible: Always
Steps to Reproduce:
Comment 1 Riku Palomäki 2004-10-24 05:31:52 UTC
Created attachment 42487 [details, diff]
The patch for emerge
Comment 2 Jason Stubbs (RETIRED) gentoo-dev 2004-10-24 06:07:41 UTC
I modified the patch a fair bit, but I've been meaning to do this for some time now. Thanks for the reminder. :)
Comment 3 Riku Palomäki 2004-10-24 12:38:25 UTC
Heh, "modified" is a weak word for what Jason did, but that CVS version works fine and is smarter than one written by me.
Comment 4 Jason Stubbs (RETIRED) gentoo-dev 2005-07-14 05:47:38 UTC
Fixed on or before 2.0.51.22-r1 
Comment 5 Jason Stubbs (RETIRED) gentoo-dev 2005-07-14 06:58:26 UTC
Looking through the batch of bugs, I'm not sure that some of these are 
actually fixed in stable. Others, the requirements have possibly changed after 
the initial fix was committed. 
 
If you think this bug has been closed incorrectly, please reopen or ask that 
it be reopened.