Re: Conffiles and Configuration files (again)
On Tue, 7 Apr 1998, Philip Hands wrote:
> OK, an example where it might make sense to have a non-configuration file,
> listed as a conffile:
>
> A package includes a script (under /usr/bin say) that is commonly
> customised by the local admin.
>
> Mgetty's faxrunqd used to be like this, because it had the fax ports
> hardwired in the script.
>
> I know this probably counts as a bug in itself, but if that is the standard
> procedure for users of this package on other OS's, you can expect them to feel
> free to hack the script on Debian too. This is a reason to list it as a
> conffile, so that if they do go ahead and edit a script, they get warned
> before it is overwritten.
>
> If the admin does not edit the script, they will never find out about it being
> a conffile, but if they do, it will save them from a lot of wasted effort when
> they upgrade.
No, this script should not be a conffile. Any customisation, such as fax
ports, should be read from a configuration file somewhere under /etc. If a
script in /usr/bin requires customisation by the sysadmin, this is a bug
in the script.
Remco
--
To UNSUBSCRIBE, email to debian-policy-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: