* Philip Webb <purs...@ca.inter.net>
Portage regularly demands config files be update :
no problem, I always use 'etc-update'.
However sometimes, it then says :
root:523 ~> etc-update
Scanning Configuration files...
Automerging trivial changes in: /etc/nanorc
Exiting: Nothing left to do; exiting. :)
Whyever doesn't Portage make that decision in the first place
& save users an extra step or steps, if there are several such files ?
Is there a reason or should I file a bug ?
I suppose it's because etc-update doesn't run automatically after
running emerge. At the time it's telling you to run etc-update it's not
aware of what changes there are, if they're trivial, or how you've
configured etc-update via /etc/etc-update.conf. It's just aware that
there are changes.
Maybe you could write a wrapper for emerge that'll just append
'etc-update --preen', that way you won't be bothered again.
$ etc-update --help
etc-update: Handle configuration file updates
Usage: etc-update [options] [paths to scan]
If no paths are specified, then ${CONFIG_PROTECT} will be used.
Options:
-d, --debug Enable shell debugging
-h, --help Show help and run away
-p, --preen Automerge trivial changes only and quit
-q, --quiet Show only essential output
-v, --verbose Show settings and such along the way
-V, --version Show version and trundle away
--automode <mode>
-3 to auto merge all files
-5 to auto-merge AND not use 'mv -i'
-7 to discard all updates
-9 to discard all updates AND not use 'rm -i'