A progress meter for ebuilds should, in some manner, indicate what percentage of the code has already been compiled. I dont know how gcc works, or the mechanics of the automade programs... maybe this can be done by figuring out how many output files have to be created and how many have, in reality, been created... or recording how much of the source code has been inputted into the compiler... pretty blue sky but I think it'd be very very very cool :) Aniruddha Karim Shankar
This would become feasible if the number of output lines of a "normal" build (more or less standard use flags) were saved as a metric by the ebuild committer. So this depends on bug #3585 for logging support and bug #2905 also requires storing some kind of building information.
What would do it for my is that it just shows how many packages it already installed. So that you emerge something with 20 dependencies still to build (or you update for the first time since long), it would say something like "Installed 3 out of 20 packages". The only problem i see is that it would be very difficult for this to be handy AND output all current output to the terminal.
*** Bug 8333 has been marked as a duplicate of this bug. ***
Portage loggin features in 2.0.42 will take care of this. Carries a count of (done/total).
