Bug#40766: Rewrite of "configuration files" section

[Stefan Gybas <cab@studbox.uni-stuttgart.de>]

Hamish Moffatt wrote:

> In short, you may not automatically modify the conffile of another package,
> either from your postinst or from a program called from your postinst.
> [...]
> It's a very friendly solution, but later dpkg will ask them about upgrading
> configuration files they've never heard of. You should lobby the maintainer
> of the package's conffile you want to modify to give you a mechanism
> (like updated-inetd etc) to do so.

So if this update-inetd program modifies a conffile, I am not allowed to
call it from my postinst? What's the reason for such a program then?

This looks like the only clean solution would be to provide update-*
programs and not to mark the configuration files as conffiles. But this
means that update-* programs should not modify conffiles at all.

-- 
Stefan Gybas