On Sun, 24 Nov 2002, Marc Haber wrote:
> The reason for this request is a packaging issue for building Debian
> packages for exim4. Debian has a nice program, debconf, which allows
> to ask the user during package installation for configuration options.
> If we want to be able to change the answers to these questions later,
> we need to generate the exim config file during package installation.
> An automatically generated config file should not be in /etc as
> mandated by the FHS, it should be in /var.
>
> We also want people with more exim knowledge to be able to use their
> own configuration file. Currently, we have a script that copies a
> exim.conf.template from /etc to /var and does some modifications.
> There is a possibility to have that script take the exim.conf.template
> unaltered to /var if the user has written her completely own exim
> configuration. I consider this very ugly, and would prefer to have
> exim only look for the /var config file if none is found in /etc. This
> could be accomplished by implementing the change to CONFIGURE_FILE in
> Local/Makefile, which won't break existing setups.
Could you do this by shipping a default /etc/exim.conf which is simply:
.include /var/exim.conf
then the exim binary would not need to look in /var ?
(I don't imagine that the overhead on an include is very different from
that of looking for more than one file.)
--
Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge
A.C.Aitchison@??? http://www.dpmms.cam.ac.uk/~werdna
