On Wed, 20 Apr 2011 20:12:21 -0500
Donnie Berkholz <dberkholz@g.o> wrote:

> From a glance over the guide, it wasn't immediately obvious what in 
> there would result in a broken system. Perhaps it's the "run 
> dispatch-conf" that's buried in the middle of a paragraph without
> enough emphasis? That's particularly confusing for people who use
> etc-update instead, and it *needs* to move somewhere more obvious
> like a separate code listing with big <important> tags and bold text.
> The line of red text just isn't enough, it needs to stand out even
> more.

I have converted all my systems to baselayout-2/openrc now, and on all
of them, the very /last/ message shown after the emerge run is that "[x]
important configuration files [in /etc]" need to be updated.

I would think that Gentoo users are already primed to this message and
that they would respond accordingly. Even when it's dozens of packages
you have updated, this message should stand out, because it's basically
the first one you read scrolling back up.

> One potential cleaner approach to the same idea Kfir suggested is to 
> make it an interactive emerge with an ACCEPT_LICENSE-like feature
> that pops up something you must read and agree to.

I've been thinking about an openrc mechanism that refuses rebooting
(reboot, halt, which are calls that openrc handles)
when /etc/{conf,init}.d files have not been updated. Anyone game to get
coding? :)


     jer