Bug#162120: Support #162120

[Bill Allombert <allomber@math.u-bordeaux.fr>]

On Tue, Jul 08, 2003 at 10:47:35AM -0500, Manoj Srivastava wrote:
> 	This, then, has all the negatives that ajt seems to think that
>  not regenerating configuration files has. And would not work in the
>  corner case where mere presence of a file changes program behaviour
>  (though I do not know, off hand, if there are any instances of this
>  behaviour out there -- /etc/nologin does not have the problem, since
>  no one would rationally want to recreate that)

Setting up automount at my lab is just a matter of 'rm /etc/auto.master'.
If automount were to recreate this file on upgrade, it would break
the system.  Nullmailer has a similar property. 

In both there are probably other ways to proceed, but why a sysadmin should 
maintain a config file when none is enough ?

In fact, having a directory (/etc/foo) composed of small config files
that are queried via if [ -f /etc/foo/bar ]; has its merit (easy to handle
in maintainer scripts). This just rely on not adding back removed
files.

Cheers,
-- 
Bill. <ballombe@debian.org>

Imagine a large red swirl here.