{"id":3,"date":"2006-10-07T05:30:10","date_gmt":"2006-10-07T02:33:26","guid":{"rendered":""},"modified":"2017-03-07T16:01:55","modified_gmt":"2017-03-07T16:01:55","slug":"elog-no-excuses","status":"publish","type":"post","link":"https:\/\/blogs.gentoo.org\/aross\/2006\/10\/07\/elog-no-excuses\/","title":{"rendered":"elog &#8211; endless possibilities and no excuses."},"content":{"rendered":"<p>I don&#8217;t believe in holding the hands of users running <em>~arch<\/em> &#8211; even if they only have a few <em>~arch<\/em> ebuilds on an otherwise stable system. While <strong>ALL<\/strong> Gentoo users should be reading the messages delivered via <code>ewarn<\/code>, for <em>~arch<\/em> users this can be critical.<\/p>\n<p>With the introduction of the elog logging framework in portage-2.1.1, there&#8217;s no excuse for missing these messages. <a href=\"http:\/\/gentoo-wiki.com\/Make.conf.example\">make.conf.example<\/a> shows how to automatically save ebuild messages to disk, or email them to an address of your choosing. <a href=\"http:\/\/bugs.gentoo.org\/show_bug.cgi?id=136496\">elogviewer<\/a> provides a <a href=\"http:\/\/maxima.wordpress.com\/files\/2006\/06\/elogviewer.png\">nice GUI<\/a> for reviewing messages, while <a href=\"http:\/\/www.gentoo-portage.com\/app-portage\/portage-mod_jabber\">portage-mod_jabber<\/a> allows you to receive them via XMPP (Jabber).<\/p>\n<p>Should you want to, there&#8217;s no reason why you couldn&#8217;t easily receive ebuild messages via SMS or pager &#8211; they could even be posted to a blog using the <a href=\"http:\/\/en.wikipedia.org\/wiki\/MetaWeblog\">MetaWeblog API (MWA)<\/a>, or sent directly to your workstation screen using <a href=\"http:\/\/www.pykota.com\/software\/pykoticon\">PyKotIcon<\/a> or <a href=\"http:\/\/remotegrowl.erlang.no\/\">Remote Growl<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I don&#8217;t believe in holding the hands of users running ~arch &#8211; even if they only have a few ~arch ebuilds on an otherwise stable system. While ALL Gentoo users should be reading the messages delivered via ewarn, for ~arch users this can be critical. With the introduction of the elog logging framework in portage-2.1.1, &hellip; <a href=\"https:\/\/blogs.gentoo.org\/aross\/2006\/10\/07\/elog-no-excuses\/\" class=\"more-link\">Continue reading <span class=\"screen-reader-text\">elog &#8211; endless possibilities and no excuses.<\/span><\/a><\/p>\n","protected":false},"author":52,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[3],"tags":[],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/blogs.gentoo.org\/aross\/wp-json\/wp\/v2\/posts\/3"}],"collection":[{"href":"https:\/\/blogs.gentoo.org\/aross\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.gentoo.org\/aross\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.gentoo.org\/aross\/wp-json\/wp\/v2\/users\/52"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.gentoo.org\/aross\/wp-json\/wp\/v2\/comments?post=3"}],"version-history":[{"count":1,"href":"https:\/\/blogs.gentoo.org\/aross\/wp-json\/wp\/v2\/posts\/3\/revisions"}],"predecessor-version":[{"id":15,"href":"https:\/\/blogs.gentoo.org\/aross\/wp-json\/wp\/v2\/posts\/3\/revisions\/15"}],"wp:attachment":[{"href":"https:\/\/blogs.gentoo.org\/aross\/wp-json\/wp\/v2\/media?parent=3"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.gentoo.org\/aross\/wp-json\/wp\/v2\/categories?post=3"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.gentoo.org\/aross\/wp-json\/wp\/v2\/tags?post=3"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}