On Thu, 4 Dec 2003, Tom Kistner wrote:
> > limited; nobody is going to type
> >
> > ./configure --many --different --settings
> >
> > every time they build Exim. If they had to, they'd keep the command in a
>
> You usually don't need more than 2 or 3 options there.
Indeed, for the sort of packages that use it. However, for Exim, there
are quite a number of things that are regularly specified at compile
time by admin choice.
On the relatively simple configuration where I am now (no
authentication, no databases, no TLS, no fancy DBMs, almost a 'basic'
Exim), there are still 10 non-default settings that have to be
specified, none of which autoconf could find for itself because they are
admin choices. They are:
BIN_DIRECTORY=/opt/exim/bin
CONFIGURE_FILE=/etc/mail/exim.configure
EXICYCLOG_MAX=28
EXIM_GID=822
EXIM_UID=822
EXIM_MONITOR=eximon.bin
EXIWHAT_EGREP_ARG=' exim( |$$|-)'
LOOKUP_CDB=yes
ROUTER_IPLOOKUP=yes
SPOOL_MODE=0640
> In some (most?) cases, if falls flat on its face, however. And THEN the
> pain starts. Prominent example being RH systems sticking OpenSSL stuff
> in all kinds of funky places, and vanilla ./configure looking for it in
> the standard /usr/local/openssl tree ...
That's also a problem, but even if it finds OpenSSL, the admin may not
want to build Exim with SSL support.
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
Get the Exim 4 book: http://www.uit.co.uk/exim-book
