Summary: | remove etc-update from emerge output, use dispatch-conf | ||
---|---|---|---|
Product: | Portage Development | Reporter: | nm (RETIRED) <nightmorph> |
Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | a3li, bkohler, docs-team |
Priority: | Normal | Keywords: | InVCS |
Version: | 2.1 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 409383 |
Description
nm (RETIRED)
2012-01-14 05:34:34 UTC
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. |