as stated. emerge's output should no longer mention etc-update at all, as the tool is just too dangerous to use. the documentation team and the developers have been in agreement about this for awhile...which is why we changed all the online handbooks/documentation to reflect using dispatch-conf instead of etc-update. we did this four years ago, actually: http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-portage-tools.xml?r1=1.9&r2=1.10 please...do it for the users. we don't need them to hose their systems again by accidentally wiping all their config files, which etc-update makes all too easy. we need some consistency with the handbook's instructions. thanks!
looks like the "autounmask" output always tell users to run etc-update, too.
huh? what's wrong with etc-update?
never needed dispatch-conf for anything, etc-update is more than enough and not dangerous at all -> resolved, wontfix
It shouldn't be very difficult to add support to etc-update for /etc/config-archive, which will make it just as safe as dispatch-conf.
(In reply to comment #1) > looks like the "autounmask" output always tell users to run etc-update, too. Yeah, I put it there, because it's what I have always used. In comment #0 you talk about some bogus behavior, but I can't find any bug about it and in all the time I watch dev-portage@g.o never have seen anything close to "etc-update wiped my /etc/portage". Could you elaborate on this?
I find that for new(ish) users, dispatch-conf is both more intuitive and (currently) safer. Is there anything wrong with changing messages to simply read "Please use dispatch-conf or etc-update to merge configuration file changes"?
our emerge output should be in sync with the documentation. if we've suggested people move over to dispatch-conf, and new users are having a better time as a result, then it probably is worthwhile to update the text. for us "old timers", the warning message isn't going to make a lick of a difference. as for extending etc-update, i think we should split that bug off. personally, i'm stuck in my ways, at least for now ...
(In reply to comment #7) > our emerge output should be in sync with the documentation. if we've > suggested people move over to dispatch-conf, and new users are having a > better time as a result, then it probably is worthwhile to update the text. Okay, done: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=ea26df1ef9b3dcb7a6a45b487342cc7149a77be5 > as for extending etc-update, i think we should split that bug off. Yeah, good idea.
This is fixed in 2.1.10.52 and 2.2.0_alpha96.
thanks, guys.
