| 1 |
* Philip Webb <purslow@××××××××.net> |
| 2 |
|
| 3 |
>Portage regularly demands config files be update : |
| 4 |
>no problem, I always use 'etc-update'. |
| 5 |
>However sometimes, it then says : |
| 6 |
> |
| 7 |
> root:523 ~> etc-update |
| 8 |
> Scanning Configuration files... |
| 9 |
> Automerging trivial changes in: /etc/nanorc |
| 10 |
> Exiting: Nothing left to do; exiting. :) |
| 11 |
> |
| 12 |
>Whyever doesn't Portage make that decision in the first place |
| 13 |
>& save users an extra step or steps, if there are several such files ? |
| 14 |
>Is there a reason or should I file a bug ? |
| 15 |
|
| 16 |
I suppose it's because etc-update doesn't run automatically after |
| 17 |
running emerge. At the time it's telling you to run etc-update it's not |
| 18 |
aware of what changes there are, if they're trivial, or how you've |
| 19 |
configured etc-update via /etc/etc-update.conf. It's just aware that |
| 20 |
there are changes. |
| 21 |
|
| 22 |
Maybe you could write a wrapper for emerge that'll just append |
| 23 |
'etc-update --preen', that way you won't be bothered again. |
| 24 |
|
| 25 |
$ etc-update --help |
| 26 |
etc-update: Handle configuration file updates |
| 27 |
|
| 28 |
Usage: etc-update [options] [paths to scan] |
| 29 |
|
| 30 |
If no paths are specified, then ${CONFIG_PROTECT} will be used. |
| 31 |
|
| 32 |
Options: |
| 33 |
-d, --debug Enable shell debugging |
| 34 |
-h, --help Show help and run away |
| 35 |
-p, --preen Automerge trivial changes only and quit |
| 36 |
-q, --quiet Show only essential output |
| 37 |
-v, --verbose Show settings and such along the way |
| 38 |
-V, --version Show version and trundle away |
| 39 |
|
| 40 |
--automode <mode> |
| 41 |
-3 to auto merge all files |
| 42 |
-5 to auto-merge AND not use 'mv -i' |
| 43 |
-7 to discard all updates |
| 44 |
-9 to discard all updates AND not use 'rm -i' |
Archives