On Fri, 16 Oct 1998, Julian wrote:
> Someone pointed out that exim was getting somewhat 'bloated' these days.
> Personally I don't agree, in that almost all of the new features are ones
> that I am interested in. However, in the same way that you can choose
> which sets of databases should be supported, it would be nice if certain
> features could be chosen relatively selectively at compile time, or if you
> feel like being extra flash make them dynamic libs, or indeed make both of
> those options. As an example, we currently don't use exim filters, but there
> doesn't appear to be any way to not include the relevant code? Whilst I
> can select which directors, routers and transports are compiled in...
It is a matter of striking a balance between infinite flexibility and
complication inside the source. I don't want Exim to be cluttered up
with 1001 #ifdefs. Having said that, the filter code is quite a large
chunk, so it does make some sense to leave it out of the binary if you
are not using it. I'm not sure that there's very much else that could
conveniently be omitted.
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
--
*** Exim information can be found at
http://www.exim.org/ ***
