Why would you want to run sasl2? IMHO sasl2 in cooker is a joke. Not one package (except cyrus-sasl) is using it:
For the Requires (of the binary packages) only cyrus-sasl-2.1.10-2mdk requires libsasl2. The rest requires libsasl7:
apache2-2.0.44-6mdk.i586.rpm apache2-common-2.0.44-6mdk.i586.rpm apache2-mod_php-2.0.44_4.3.1-2mdk.i586.rpm apache2-mod_ssl-2.0.44-6mdk.i586.rpm autofs-4.0.0-0.18mdk.i586.rpm balsa-2.0.8-1mdk.i586.rpm cyrus-sasl-2.1.10-2mdk.i586.rpm directory_administrator-1.3.5-1mdk.i586.rpm evolution-1.2.2-1mdk.i586.rpm gnomemeeting-0.96-2mdk.i586.rpm gnupg-1.2.1-2mdk.i586.rpm kdebase-3.1-50mdk.i586.rpm kdelibs-3.1-33mdk.i586.rpm libldap2-2.0.27-4mdk.i586.rpm libuser1-0.51-6mdk.i586.rpm nss_ldap-202-1mdk.i586.rpm openldap-clients-2.0.27-4mdk.i586.rpm openldap-servers-2.0.27-4mdk.i586.rpm pam_ldap-156-1mdk.i586.rpm php-ldap-4.3.0-3mdk.i586.rpm postfix-2.0.1-2mdk.i586.rpm proftpd-1.2.7-1mdk.i586.rpm sendmail-8.12.7-3mdk.i586.rpm squid-2.5.STABLE1-7mdk.i586.rpm userdrake-0.5-5mdk.i586.rpm
and when you look at the BuildRequires of the src.rpm packages:
libsasl-devel (can be libsasl2-devel or libsasl7-devel):
evolution-1.2.2-1mdk.src.rpm /usr/bin/ld: cannot find -lsasl kdelibs-3.1-33mdk.src.rpm libuser-0.51-6mdk.src.rpm breaks squid-2.5.STABLE1-7mdk.src.rpm breaks
libsasl7-devel:
apache2-2.0.44-5mdk.src.rpm /usr/bin/ld: cannot find -lsasl apache2-mod_php-2.0.44_4.3.1-2mdk.src.rpm balsa-2.0.8-1mdk.src.rpm /usr/bin/ld: cannot find -lsasl gnomemeeting-0.96-2mdk.src.rpm /usr/bin/ld: cannot find -lsasl kdebase-3.1-50mdk.src.rpm nss_ldap-202-1mdk.src.rpm builds OK, but with no sasl support openldap-2.0.27-4mdk.src.rpm checking for sasl.h... no php-ldap-4.3.0-3mdk.src.rpm BuildRequires not needed postfix-2.0.1-2mdk.src.rpm cannot find -lsasl sendmail-8.12.7-3mdk.src.rpm sasl.h: No such file or directory
See, none of the packages currently build with sasl2.
I installed rh8.0 in a vmware this week and found out that their sasl package contains both sasl7 and sasl2. They just let it coexists.
Brian's comment about this: > And it does not break stuff? The problem with the two sasls co-existing > is not merely a packaging issue. There are re-entrancy problem with an > application chain that needs to use both sasls. Cyrus/LDAP/Postfix > exhibit this problem for instance.
> But this does not solve the overall problem of a chain of applications > needing common sasl authentication yet using different versions of the > library.
> There is lots of information on the problem on the cyrus mailing list. Try
> googling for "sasl re-entrancy" (http://www.google.com/search?q=sasl%20re-entrancy
> to get a better handle on the real problem.
So... What is mdk going to do? I would recommend to put sasl7 back and drop sasl2 for now. At least put the src.rpm for the sasl7 packages back --> it's missing!
regards,
Stefan
smime.p7s
Description: S/MIME Cryptographic Signature
