Bug#927395: Do not touch(1) update-exim4.conf.conf for no good reason

[積丹尼 Dan Jacobson]

retitle 927395 #include update-exim4.conf.conf-user.pre
thanks

Anyway having a robot edit what the user edits what the robot edits...
often leads to disaster.

A much cleaner design for update-exim4.conf.conf would be something like

#include user.pre  #if exists
...guts go here...
#include user.post #if exists

Where user.* are guaranteed not to be tampered with by the robot.
Or even use user.pre.d/ user.post.d/ and then even upon package removal
dpkg would say "...d/ not removed as it was not empty." This fulfilling
the promise to never tamper with them.

Yes you could say the user could just put the #include lines into
update-exim4.conf.conf himself. But that still means he and the robot
are still editing the same file... so he can't use his version control
system on it.

P.S., https://www.google.com/search?q=UE4CC+debian only finds exim.