Well, I know I'm asking for a few flames here, but, this
idea just popped into my head and I cannot get rid of it.


When you sync and update a system that has not been updated for
a while, you get many packages to upgrade. OK usually not a problem.
However, myself (and many other folks) are rather lazy: we do
not watch the terminal session for hours, looking for those tidbits
of info of little pesky admin things to do upon updating a package
(let alone dozens of packages).

We are also lazy: we do not parse the log files looking for those
'little pesky admin things to do upon updating a package'
either.


Much pain results for lots of regular folks, like forgetting to
run 'python-updater'. So any ideas on an enhancement/fix?


Why, could the dev add an option that parses out all of those
pesky admin things into either a singular log file? Or better
yet, a gui popup that lists just those instructions for each
package. Then a lazy admin could go through them, take whatever
action necessary, and then just kill the pop-up.

Just a thought, I figured I'd put up here for discussion. In fact
some of the younger/sharper minds should come up with an even
slicker way for those instructions to hang around, so that us
lazy admins are forced into a convenient click or 2 to dismiss
these little pesky admin caveats....?

thoughts?



James

On Thu, 28 Aug 2008 21:22:00 +0000 (UTC), James wrote:

> Why, could the dev add an option that parses out all of those
> pesky admin things into either a singular log file? Or better
> yet, a gui popup that lists just those instructions for each
> package. Then a lazy admin could go through them, take whatever
> action necessary, and then just kill the pop-up.

Do you mean like the elog system that can write this information to a
separate log file, email it to you, pass it to a command or any
combination of these? There are also elog viewers in portage, although I
have no experience of these, I use my mailer to read these messages.


--
Neil Bothwick

Windows Error #09: Game Over. Exiting Windows.

Neil Bothwick wrote:

On Thu, 28 Aug 2008 21:22:00 +0000 (UTC), James wrote:



Why, could the dev add an option that parses out all of those
pesky admin things into either a singular log file? Or better
yet, a gui popup that lists just those instructions for each
package. Then a lazy admin could go through them, take whatever
action necessary, and then just kill the pop-up.



Do you mean like the elog system that can write this information to a
separate log file, email it to you, pass it to a command or any
combination of these? There are also elog viewers in portage, although I
have no experience of these, I use my mailer to read these messages.



I concur elog is great. I have it e-mail me a single file after I've run
updates or installed anything. It's stupid simple to setup too.



--Joshua Doll

Joshua D Doll wrote:

Neil Bothwick wrote:

On Thu, 28 Aug 2008 21:22:00 +0000 (UTC), James wrote:



Why, could the dev add an option that parses out all of those
pesky admin things into either a singular log file? Or better
yet, a gui popup that lists just those instructions for each
package. Then a lazy admin could go through them, take whatever
action necessary, and then just kill the pop-up.



Do you mean like the elog system that can write this information to a
separate log file, email it to you, pass it to a command or any
combination of these? There are also elog viewers in portage, although I
have no experience of these, I use my mailer to read these messages.



I concur elog is great. I have it e-mail me a single file after I've
run updates or installed anything. It's stupid simple to setup too.



--Joshua Doll




I use elogviewer myself. Works pretty good. I can also clear out the
old logs when I have everything updated and stable as well. Gives me a
fresh start for next time.


Dale

:-) :-)

Joshua D Doll wrote:

Neil Bothwick wrote:

On Thu, 28 Aug 2008 21:22:00 +0000 (UTC), James wrote:



Why, could the dev add an option that parses out all of those
pesky admin things into either a singular log file? Or better
yet, a gui popup that lists just those instructions for each
package. Then a lazy admin could go through them, take whatever
action necessary, and then just kill the pop-up.



Do you mean like the elog system that can write this information to a
separate log file, email it to you, pass it to a command or any
combination of these? There are also elog viewers in portage, although I
have no experience of these, I use my mailer to read these messages.



I concur elog is great. I have it e-mail me a single file after I've run
updates or installed anything. It's stupid simple to setup too.


Sounds like a really useful tool, but I can't see where to get it.

According to eix, the only elog tools are direct viewers. I'd really
like one that can email me, where can I find it?


Thanks

Matt

Matt Harrison wrote:

Joshua D Doll wrote:

Neil Bothwick wrote:

On Thu, 28 Aug 2008 21:22:00 +0000 (UTC), James wrote:



Why, could the dev add an option that parses out all of those
pesky admin things into either a singular log file? Or better
yet, a gui popup that lists just those instructions for each
package. Then a lazy admin could go through them, take whatever
action necessary, and then just kill the pop-up.



Do you mean like the elog system that can write this information to a
separate log file, email it to you, pass it to a command or any
combination of these? There are also elog viewers in portage,
although I

have no experience of these, I use my mailer to read these messages.



I concur elog is great. I have it e-mail me a single file after I've
run updates or installed anything. It's stupid simple to setup too.


Sounds like a really useful tool, but I can't see where to get it.

According to eix, the only elog tools are direct viewers. I'd really
like one that can email me, where can I find it?


Thanks

Matt





I don't use the email feature but I got this from man make.conf:

PORTAGE_ELOG_CLASSES

PORTAGE_ELOG_SYSTEM

PORTAGE_ELOG_COMMAND

PORTAGE_ELOG_MAILURI

PORTAGE_ELOG_MAILFROM

PORTAGE_ELOG_MAILSUBJECT
Please see /usr/share/portage/config/make.conf.example for
elog documentation.


I would look at the make.conf.example file to see how to set that up.

Dale

:-) :-)

Dale <dalek1967 <at> bellsouth.net> writes:


> >>> Do you mean like the elog system that can write this information to a
> >>> separate log file, email it to you, pass it to a command or any
> >>> combination of these? There are also elog viewers in portage,


OK elog look good.
Is this the best wiki to
use to initailly set it up?


http://gentoo-wiki.com/TIP_Making_portage_use_/usr/sbin/sendmail_to_send_out_ELOG_mails


?

James

On Fri, 29 Aug 2008 00:46:36 +0000 (UTC), James wrote:

> OK elog look good.
> Is this the best wiki to
> use to initailly set it up?

> http://gentoo-wiki.com/TIP_Making_portage_use_/usr/sbin/sendmail_to_send_out_ELOG_mails

Hardly "the TIP is now obsolete! See /etc/make.conf.example for further
details."


--
Neil Bothwick

The opposite of a profound truth may well be another profound truth. *
Bohr

On Friday 29 August 2008, Neil Bothwick wrote:
> On Fri, 29 Aug 2008 00:46:36 +0000 (UTC), James wrote:
> > OK elog look good.
> > Is this the best wiki to
> > use to initailly set it up?
> >
> > http://gentoo-wiki.com/TIP_Making_portage_use_/usr/sbin/sendmail_to_send_
> >out_ELOG_mails
>
> Hardly "the TIP is now obsolete! See /etc/make.conf.example for further
> details."

I think my set up is pretty vanilla: at the end of an emerge -uDv world I get
a concatenated list of all the elog comments. Unless I shut down the
terminal/console I cannot avoid but scrolling upwards to see what's asked of
me by the package maintainers following the emerge. Isn't this enough for
your needs?

Sure, if I have a major breakage I will start looking
through /var/log/portage/<package_name> to see what went wrong in detail,
otherwise I follow the invariably trivial recommendations at the end of the
emerge.
--
Regards,
Mick