Figured I’d visit forums today, seen at least 4 topics about lost menus while updating gnome-menus to 2.26.2, banged head 4 times because of users not reading elog messages and doing random fixes instead of searching the real cause of the change (in changelog, ebuild, elog, bugzilla). Good thing I have added that to the migration guide that will be up for stable users.
For those of you who still don’t know about elog, man make.conf.
Update: fix typo.
You mean «man make.conf» ?
I assume you meant “man make.conf”, not “make make.conf”
Also, as a side note, I couldn’t get the comment form to accept my gmail address.
“man make.conf”? Though it just points people to /usr/share/portage/config/make.conf.example anyways.
Don’t you mean “man make.conf”? 😛
You mean, “man make.conf”? 🙂
> «man make.conf» ?
yes, fixed, thanks for pointing it 🙂
> Though it just points people to /usr/share/portage/config/make.conf.example anyways.
true, but it gives the occasion to look at other documented variables 🙂
> Also, as a side note, I couldn’t get the comment form to accept my gmail address.
you’ll need to check with infra since it’s a gentoo hosted blog.
Unfortunately, elog is widely used to display useless spam, making it as useless as einfo used to be. That’s one thing news items have going for them — it’s much harder for developers to add gratuitous noise that way, so most news items that users see are really relevant. At least currently…
@Ciaran, I was actually meaning elog as a framework.
The message is classified as ewarn, which I consider should be always read. If the feature is over-used to display not so important messages, bugs should be filled about those ebuilds. News items require a lot more time to get into the tree which is obviously what stopped me from using it for ~arch users but now that most cases are properly documented (thanks to users who read the message), the stabilization of gnome 2.26 will have a news item pointing at the migration guide which repeats this info without requiring a merge.
i use app-portage/portage-mod_jabber as elog system – fantastic way to read portage logs via IM-client. But it not show QA & some info messages…
@evadim, sounds like a setup issue, logged messages are configurable per level (log, info, warn, …).
@Gilles Dartiguelongue
i guess not, in my make conf:
PORTAGE_ELOG_CLASSES=”info warn error”
and from some ebuilds i see info, from other – not
@evadim, you might want to fill a bug report then.
@evadim: you don’t have “qa” in PORTAGE_ELOG_CLASSES, that’s why you don’t see those messages. You also don’t have “log” in there, so maybe those “info” messages that you miss are actually “log” messages?
From /usr/share/portage/config/make.conf.example:
# logging related variables:
# PORTAGE_ELOG_CLASSES: selects messages to be logged, possible values are:
# info, warn, error, log, qa, *
# Warning: commenting this will disable elog