Please do not reassign bugs around!

It takes only a few lines, yes. But it unconditionally makes exim
bigger, and adds an RPM dependency. I'm not sure that many people would
want that.

Debian has a patch which adds dynamical loading, but I'm not keen on
maintaining an external patch either.

We could build it twice.
As exim is in the Build Service now, 
http://software.opensuse.org/download/server:/mail/
it wouldn't be an issue of CD space anymore.

Opinions?

I use mysql lookup for exim (together with mysql-authentication for courier-imap see bug 188587 (added in 10.2)) in a productive environment on a suse 9.3 box. 
Using a mysql-db is a really good thing for virtualuser mailsystems! 

Mysql support can be used for a lot of useful things:
- spam-blacklists
- domain administration (smtp-forward, catchall, etc.)
- autoresponders
...

I build the original an the mysql-enabled exim for 10.1 to compare the size:
exim-4.51-21.i586.rpm:
original:   1079787 
with mysql: 1081707 (+1.9kB 0.18%)

/usr/sbin/exim
original:   778180
with mysql: 782432  (+4.2kB 0.5%)

So: size is not a big issue.

       USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
w/o:   mail     32552  0.0  0.4   6720  1136 ?        Ss   23:53   0:00 /usr/sbin/exim -bd -q5m
with:  mail     32617  0.0  0.4   8044  1224 ?        Ss   23:54   0:00 /usr/sbin/exim -bd -q5m


Since the mysql library is loaded dynamically, it doesn't really add to
the binary or rpm size. But it makes the process bigger at runtime.


The mysql library also pulls in other libraries that it is linked
against... and those are at least:

exim      32617       mail  mem       REG      253,3  1283312     442510 /usr/lib/libmysqlclient.so.15.0.0
exim      32617       mail  mem       REG        3,2   180631      44405 /lib/libm-2.4.so
exim      32617       mail  mem       REG        3,2    47259      44393 /lib/libcrypt-2.4.so
exim      32617       mail  mem       REG        3,2    87850      44411 /lib/libnsl-2.4.so
exim      32617       mail  mem       REG        3,2    70512      44465 /lib/libz.so.1.2.3

So that's a 20-30 % increase in runtime process size.
Something which many people could live with, but lean package
dependencies are also important. You don't want to install mysql,
postgresql, X11, Java, Mono, whatnot on every machine... 

And since mysql support cannot be split off into a module (and
subpackage), I still advocate the separate specfile solution.

It is now built in the buildservice as a variant.
See http://software.opensuse.org/download/server:/mail/SuSE_Linux_Factory/

I meanwhile think that it is better to build both binaries in the same
spec, put them in subpackages, and use update-alternatives, because this
avoids other issues (including a forest of %ifs in the specfile).
But for the moment, I'm fine with the way I'm doing it now, because I
wanted to play with linked packages in the buildservice anyway.
BTW, autobuild will have only the standard exim package for now, so the
mysql-enables binary will be in the BS. Is that okay for you?

Yes! Thanks very much. 
How and where are special packages in the BS announced?
I mean how people find out in general, if there are variants of installable packages?

I just looked into the SPEC of the BS package and the changelog.
You did a lot of work on the new version! I will try it, specially looking forward to the eximstat reports.

> How and where are special packages in the BS announced?

The BS is still work in progress, there is no announcement or search
mechanism yet, but it will come in the future :)

I'm closing this bug now, since exim-mysql is in the build service, and
the exim package containing the needed changes for that is submitted to
Factory.