[I forgot to address these points, sorry]
OK,
clear to understand, but there are some drawbacks. First, sasl1 can no longer use the password file (sasldb) from privious versions (now sasl1 uses gdbm, previous versions used db3.3) and there is no easy way to solve. To compile sasl2 you need db4.0 devel package, but sasl1 does not support db4.0. To
Not really, cyrus sasl v2 can compile against libdb 3.3 (in fact db4 support has been a recent addition and compiling it against db4 will probably mean that dbconverter2 won't work, but I didn't test this transition. I did test my solution to bug 2410).
solve this, I had to grab the SRPM from mdk9.0 and replaced the mdk9.1 sasl1 packages. And there I can use my ldap patch for the sasl1 stuff.
Also libdb3.3-devel should be still present in 9.1 (pam for example uses it), so it should be just a matter of changing the buildrequire.
Bye
-- Luca Olivetti Note.- This message reached you today, it may not tomorrow if you are using MAPS or other RBL. They arbitrarily list IP addresses not related in any way to spam, disrupting Internet connectivity. See http://slashdot.org/article.pl?sid=01/05/21/1944247 and http://theory.whirlycott.com/~phil/antispam/rbl-bad/rbl-bad.html
pgp00000.pgp
Description: PGP signature
