On Sun, 7 Jan 2007 17:26:12 +0100 Thilo Bangert <[EMAIL PROTECTED]> wrote:
> Marius Mauch <[EMAIL PROTECTED]> said: > > Just a heads up that in the coming weeks I'll start checking > > packages that still use einfo for important messages and convert > > them to elog if appropriate. > > whats the policy? when do i use einfo and when elog? > > the dev handbook states for einfo: > > Inform the user about something important. The argument given to > einfo is the message that the user will see. Do not use einfo to > display banners such as > "*************************************". The fact that you're using > einfo is enough to get the user's attention. > > and says nothing about elog (AFAICT)... Hmm, I thought I got the dev handbook updated some time ago ... Basically if it's for the user to read use elog, if it's just a status message (like "applying patch", "nothing to do here", "performing xyz") that isn't of any use after the build use einfo. > will einfo reporting to the elog framework be turned off in the > future? No. However einfo logging is not enabled by default, and right now people miss some important information if they don't enable it (but also get a lot of useless messages). Marius -- gentoo-dev@gentoo.org mailing list
