1 |
What happens to files within the scope of CONFIG_PROTECT if I don't |
2 |
execute dispatch-conf or any similar thingy? I have found the confusion |
3 |
the latter tool generates completely unsurmountable. |
4 |
|
5 |
What I'd prefer is the debian behavior: the package supplied config file |
6 |
is simply saved under a mangled name (*.dpkg-dist alongside the real |
7 |
file on debian) and I'm left to merge the changes at my convenience, |
8 |
with my preferred tools. |
9 |
|
10 |
And maybe that's what portage already does, but I'm not sure. If yes, |
11 |
where is the package supplied file saved? Is it under |
12 |
/etc/config-archive? The wiki makes the impression that |
13 |
/etc/config-archive is specific to dispatch-conf. |
14 |
|
15 |
So that's my question in a nutshell: after emerge but before |
16 |
dispatch-conf, where are the new versions of config files? |
17 |
|
18 |
-- |
19 |
Please don't Cc: me privately on mailing lists and Usenet, |
20 |
if you also post the followup to the list or newsgroup. |
21 |
To reply privately _only_ on Usenet and on broken lists |
22 |
which rewrite From, fetch the TXT record for no-use.mooo.com. |