| 1 |
On Sun, 7 Jan 2007 17:26:12 +0100 |
| 2 |
Thilo Bangert <bangert@g.o> wrote: |
| 3 |
|
| 4 |
> Marius Mauch <genone@g.o> said: |
| 5 |
> > Just a heads up that in the coming weeks I'll start checking |
| 6 |
> > packages that still use einfo for important messages and convert |
| 7 |
> > them to elog if appropriate. |
| 8 |
> |
| 9 |
> whats the policy? when do i use einfo and when elog? |
| 10 |
> |
| 11 |
> the dev handbook states for einfo: |
| 12 |
> |
| 13 |
> Inform the user about something important. The argument given to |
| 14 |
> einfo is the message that the user will see. Do not use einfo to |
| 15 |
> display banners such as |
| 16 |
> "*************************************". The fact that you're using |
| 17 |
> einfo is enough to get the user's attention. |
| 18 |
> |
| 19 |
> and says nothing about elog (AFAICT)... |
| 20 |
|
| 21 |
Hmm, I thought I got the dev handbook updated some time ago ... |
| 22 |
Basically if it's for the user to read use elog, if it's just a status |
| 23 |
message (like "applying patch", "nothing to do here", "performing xyz") |
| 24 |
that isn't of any use after the build use einfo. |
| 25 |
|
| 26 |
> will einfo reporting to the elog framework be turned off in the |
| 27 |
> future? |
| 28 |
|
| 29 |
No. However einfo logging is not enabled by default, and right now |
| 30 |
people miss some important information if they don't enable it (but |
| 31 |
also get a lot of useless messages). |
| 32 |
|
| 33 |
Marius |
| 34 |
-- |
| 35 |
gentoo-dev@g.o mailing list |
Archives