I have often found - especially during Gentoo installation - that the important messages from the ebuilds completely drown in the make/compiletion noise (autoconf, gcc etc. etc. etc.) - especially when more than one package is being emerged, as with dependencies and especially when installing Gentoo where hundreds of dependencies emerges and output rambles on and on - who here have been studying *ALL* output from *all* packages the 1++ days of installing Gentoo (with gcc, X, kde, gnome and so on and so on) - without sleeping or not paying attention? I see I am not the only one having problems with the noise drowning important messages: Taken from an current Apache bug reply: "If you read the apache-2.0.49 ebuild, you'll see that there's a warning message in there, telling you which directories you should now remove from /etc/apache2. This message unfortunately scrolls up the screen pretty quickly when you upgrade your apache installation." I think this problem would be easy to solve in many ways: 1) cache ALL ebuild messages (incl. the name of the ebuild) and output them (repeat them) when emerge is done. Simple and powerfull! 2) The alternative way: the feature -q should be working: For all ebuilds the only output should be the e-build messages. All other output should be saved and only be printed if the ebuild fails. Either 1) or 2) should be on by default in my oppinion - only developers need all the noise, ordinary users only need it when an ebuild fails and they need to file a bug report. From my non-developer user-only perspective I think 1) would be easiest - and easy to implement and yet a very nice and needed addition to Gentoo! Reproducible: Always Steps to Reproduce:
Am I the only one not fond of trying to find relevant output in 20000-30000 lines of "emerge -Uu world"-output every weeking? Am I talking to myself here? ;)
Hi, I also had thought about it, and I got the same solution idea (1). I've been stuck with some packages configuration more than once, because of missing some important messages. Some packages (as portage) beeps and waits some seconds, but it's useless if I'm out of home. I think that caching messages (or at least, saving them to a log file) should be the default behaviour. Anyone could implement this? (I've never touched python)
I was here to add this same issue, but i see its been there for a while. It annoyes me a lot, that it is not possible to distinguish usefull information from the whole bunch of compilation messages... My idea was to add simple variable which would define portage verbosity (like 0, 1, 2, and so on - starting from no output to very verbose output - possible to add to make.conf or from command line). At the moment im forced to use PORT_LOGDIR to store the whole bunch in portage log (with PORT_LOGDIR=/var/log/portage), cause i just like to know whats going on, but i dont have time to stare at the monitor all days...
Another one anoyed by this. I'm always running emerges unattended and only watch the end (etc-update messages etc). Because of that I missed for example that I *should* have run a libperl rebuild. And this is only one of these messages I missed. So please, try to report all ebuild warnings/important messages and the end also or store then in a file and tell at the end to look at the file if any important message has been logged. Kind like you currently do for the configuration changes, where you tell to run etc-update.
Please fix this! This is a truely embarrassing omission. At least someone post a some information on where those messages are stored (in the ebuild?). I found the PORT_LOGDIR solution, but that's a miserable hack. Emerge needs a "--show-messages-only" switch. OK, enough whining ;-)
Yes, this is really an important feature missing. When we can solve that issue, we could also save us alot of work with false bug reports (just because users missed the informational or warning messages).
*** This bug has been marked as a duplicate of 11359 ***
