Building an exim rpm is relatively easy. Building a generally useful
exim package is rather harder....
A.C.Aitchison@??? said:
> ***First of all the package *must not* change an existing config
> file.***
thats easy to do with rpm - although things will get more interesting
if the rpm upgrade is one that makes the config file obsolete (think
exim v2.x config files to 3.x).
my preference would be to ship half a dozen well commented template
config files for basic setups, and install *none* of them by default -
ie [using my prefered filesystem layout]
/etc/exim directory for exim configs
/etc/exim/config main config file (initially missing)
/etc/exim/config_examples directory for examples
dialup_isp
permanent_connection
smarthost
etc
d@??? said:
> I think the Debian people have done quite a nice post-install script
> which asks a few basic questions about the local setup and what Exim
> will be used for. Something like this wouldn't be a bad idea
> necessarily.
interactive post-install scripts are a no-no with rpms - and will
definitely prevent your rpms being taken up by distributors since you
can't do a full unattended install if packages start asking extra
questions.
Nigel.
--
[ - Opinions expressed are personal and may not be shared by VData - ]
[ Nigel Metheringham Nigel.Metheringham@??? ]
[ Phone: +44 1423 850000 Fax +44 1423 858866 ]
