This is not a bug, but a wish for usability improvement: from time to time some packages updated by emerge world state some important messages after being installed. When updating some dozens packages at a time some of this messages will not be read (ok, I'm lazy - but usually there is less than 1% really important stuff between all these info messages). Happend last night where xorg wanted all its drivers to be rebuilt. Not doing so I ended up with an unusabe X with no input devices available. "Rebuild drivers or your X won't work" would have been a REALLY important message. I think emerge needs a better way to report such major things so that they are clearly reported to the user and not hidden between tons of unimportant info messages. Reproducible: Always Steps to Reproduce:
It is up to the developer to pick einfo, elog, or ewarn. In this case, xorg-server used ewarn to tell you that. This is the highest visibility and up to the end user to use the info that developers give them. Portage gives you lots of options including ways to email the ewarns to you, etc.
(In reply to comment #1) > In this case, xorg-server used ewarn to tell you that. > This is the highest visibility and up > to the end user to use the info that developers give them. Portage gives you > lots of options including ways to email the ewarns to you, etc. I see that the best way the current system gives you was chosen to report this issue. Still I think this is too important to be just one or two lines inbetween several hundreds. Maybe some action list displayed after emerge is done might do the trick. Something like: "Thinkgs do do RIGHT AFTER emerge:" Another topic is that on some machines you might just have a local terminal, no X, no framebuffer. There all your warnings & compile messages simply scroll through, most of them gone within a second. - without a chance to scroll back. So there is a way to email results, but this is not the default setting. Maybe email is not available either. In the case of xorg the ewarn tells you exactly what to do. Why not offer a port for ebuilds to register scripts that can be run (user toggled?) after the emerge process? A list of available scripts might be represented right after an emerge.
We already have bug 192319 for automatic rebuilds. For higher visibility than elog messages, we have GLEP 42 news items (read with `eselect news`): http://www.gentoo.org/proj/en/glep/glep-0042.html
(In reply to comment #3) > We already have bug 192319 for automatic rebuilds. agreed, thats for automatic rebuilds. What about other maintenances stuff? Eg. ssh often urges me to delete some old certificates. > For higher visibility than > elog messages, we have GLEP 42 news items (read with `eselect news`): IMO not "visible" enough. When there is critical stuff to do you need something flashing in red, urging the user to react. Not something nice and gentle waiting in the background until someone has time to read it.
No progress, therefore closing. Feel free to reopen if you have a concrete proposal for this.
