About GWN's GLEP 42 "Critical Info" topic

[renrutal]

Dunno if this is the right place, some time ago they said Portage was closed to new requests until the next minor version, so BugZilla might not work. Also I don't know if gentoo-devel ML is open to anyone or if they'll even listen... I read most of the threads pointed by Nov 7th's GWN "Heard in the community", but it's pain to read through Gmane plus all the offtopic talk there, so it's hard to find if this has been proposed, but here goes:

This could act as last line of defense against these critical changes such as a major overhall of the config file. And yes, the user might have been warned by einfo(he was absent from the machine) and he should have been reading gentoo-announce, g.o, all the good things(maybe he didn't know), but most people just do that when it's late.

The idea: during pkg_postinst, could Portage send an email to the user, warning him about the package he just emerged?

This could be controled by PORTAGE_FEATURES(dunno what's the exact name), and have extra variables in make.conf, such as
PORTAGE_EMAILER_ADD="root@localhost;admin@foo.bar"

PORTAGE_EMAILER="mutt" // if Portage takes care of the subject and message or
PORTAGE_EMAILER="mutt -s 'Warning Will Robinson, Warning!' $PORTAGE_EMAILER_ADD $PORTAGE_WARN_MESSAGE"

I really don't know much about mutt's syntax but I hope you get the idea. Other mailing apps could be used too.

Maybe einfo could compose the message body, or a new command, ewarn or something like that.

Just that.

[Genone]

If you're just talking about einfo logging, this will very likely be in 2.0.54.