Etc-update shouldn't try to upgrade certain files like: /etc/groups, /etc/fstab, /etc/issue and similar. These files are most certainly edited by users (admins) and listing them as update pending by etc-update is pointless. Reproducible: Always Steps to Reproduce: 1. 2. 3.
sometimes we make additions to /etc/group and /etc/passwd that should be merged into systems
it would be nice if etc-update would look to see if a file in /etc has been changed after it was installed by an emerge. if the file was not modified by the user, then it's safe to use the new file. or at least have an option to "apply all updates to non-user modified files" an emerge of xfree or kde or other packages puts lots of new files into /etc which makes an etc-update very error prone. _most_ of these files are not touched ever by the user, but those that are could be held for manual review.
Comment #2 seems to have the spirit of Bug 8423 (nuke untouched files). Otherwise, I don't see why this bug is still open because etc-update should at least *inform* the user whenever a packages have collisions with CONFIG_PROTECT'ed files.
Maybe etc-update could have a config file that allows the user to specify a list of CONFIG_PROTECTED'ed files for which collisions don't matter (/etc/issue, /etc/conf.d/hostname, etc...). Then etc-update could simply remove the updates that occur in the "ignore list" with no need to prompt the user.
/etc/conf.d/hostname should really be protected. This is SO annoying having to update 16 boxes and on each I must search for that only file before entering "-5".
*** This bug has been marked as a duplicate of 114713 ***
