If a user emerges packages, the ebuild maintainers regularly like to inform users. This was always done with ewarn and einfo, but doing mass-merges (well.. multiple merges in one go) created problems. Which were fixed with elog. The thing is, that sometimes the user has to perform actions pretty much straight away. (Such as revdep-rebuilds, see comments on bug #41124) At the moment the user isn't properly informed of this. Even if elog is used, the user won't know about it until the log is viewed. I suggest that these messages should be displayed to the user in a more direct way. A possibility might be to do so in a similar manner as etc-updates are displayed at the end of the emerge output. I believe that the warn: postinst messages are most important, but am really not in a position to actually tell.
Already done, PORTAGE_ELOG_SYSTEM="echo" - upgrade your portage to 2.1.3.4 if you want this.
*** Bug 189016 has been marked as a duplicate of this bug. ***
(In reply to comment #1) > Already done, PORTAGE_ELOG_SYSTEM="echo" - upgrade your portage to 2.1.3.4 if > you want this. I am not to re-install a Gentoo just to check this, but, please make sure the default behaviour of the default profile during a fresh install sets this. That is the most improtant point for me. any way, I set up what you suggested: PORTAGE_ELOG_SYSTEM="save echo" and got nothing on screen: >>> Regenerating /etc/ld.so.cache... >>> Original instance of package unmerged safely. >>> Regenerating /etc/ld.so.cache... >>> doublehp/rpl2-4.0.0_pre1 merged. >>> No packages selected for removal by clean >>> Auto-cleaning packages... >>> No outdated packages were found on your system. * GNU info directory index is up-to-date. root@moon_gen_2:/opt/doublehp/usr/portage/doublehp/rpl2# While several Warnings have been reported by enotice .
Have you read the make.conf.example? It explains quite thoroughly what's to be done to make elog work properly. portage-2.1.3.4 made elog behave exactly as intended as explained in this bug, and approximately as in your bug. You can test by doing the following: - look in {PORTDIR} for an ebuild which posts some elog message (warn, info, qa -- depending on your config) - (re)install the package - check to see if output is appended at the bottom of emerge.
