1 |
On 27/11/2022 15:49, Mike Civil wrote: |
2 |
> On 27/11/2022 14:50, Wol wrote: |
3 |
>> Postfix afaik just has one humungous config file, so when your distro |
4 |
>> updates the config, all your local changes are trashed :-( |
5 |
>> |
6 |
>> I don't want to faff about with special copies, backups, origs etc. |
7 |
>> Everything should "just work (tm)". |
8 |
> |
9 |
> Except that portage doesn't overwrite stuff under /etc by default. It |
10 |
> saves the new config file and then tells you there's an update so you |
11 |
> can use etc-update or dispatch-conf to check/merge/abort the changes. |
12 |
> After all the new version of software may need a change to the old |
13 |
> config file. |
14 |
> |
15 |
It's not portage I'm worried about, it's me! |
16 |
|
17 |
Systemd DOES NOT PUT YOUR LOCAL CONFIG IN DANGER. |
18 |
|
19 |
Dovecot DOES NOT PUT YOUR LOCAL CONFIG IN DANGER (if you do it properly). |
20 |
|
21 |
EVERY SINGLE POSTFIX UPDATE PUTS YOUR CONFIG IN DANGER. |
22 |
|
23 |
Of course, if you're Mr Perfect you won't have a problem. Why can't |
24 |
postfix *protect* me, like systemd or dovecot do? |
25 |
|
26 |
NB - The Linux Filesystem Hierarchy (such as it is now) says that the |
27 |
distro should not be writing to /etc ! Default system state belongs in |
28 |
/usr, live system state belongs in /etc, and if the distro updates /etc |
29 |
it is basically corrupting system state. Which may or may not be |
30 |
acceptable - and here it isn't. |
31 |
|
32 |
Cheers, |
33 |
Wol |