elog – why it’s so important and why you must read it

That’s not the first post about elog, previously Gilles (eva) posted an excellent entry about that (he was a slightly angry probably :p). All these entries are published in order to warn users and they have its importance…So based on that fact it would be really nice if users start reading them 😀

Last week, I did read at least 4 bugs about a problem due the newer version of shared-mime-info (which includes a new database format)… If you as users would read your elogs, guess what? Yes you would find the solution in elog messages.

[b][size=15]Important…why ?[/size][/b]

When a developer has a important message to deliver to a set of users for a given package, usually he uses elog (elog is logged => no excuses..).
Consider the previous example with shared-mime-info, you will have a lot of problems when you try to open some files (typically gnome/kde startup) which would have not happened if you have a look at your logs.

[b][size=15]awesome… but how I can read them ?[/size][/b]

That’s seriously simple :
[*] If you’re a geek who loves GTK+ based applications (like me :p) have a look at elogviewer
[*] Use eread (c.f: man eread)

But for our sanity and peace in our souls “READ THEM” before you post a bug 🙂 .
That will help us a lot, by implicitly reducing the number of useless bugs, and in this way, we will not have to repeat things 50 times.

have fun with gentoo 😉

edit: many thanks to scarab for typos & grammar 😉