Stefan van der Eijk wrote:


I'll buy you a crate of beer if you can move it over to sasl v2... And a extra crate if you can get migrate all the other libsasl.so.7 dependancies to libsasl.so.2 in cooker.

No, I cannot, but that's how it should be done (see below).


At the moment _nothing_ in cooker (except cyrus-sasl) requires libsasl.so.2. Mdk 9.1 is going to be sasl7 based.

Pity, since it's been deprecated for over a year now (mind me, I won't be affected since I'm using saslauthd for sasl v2 and pwcheck for sasl v1, but if someone is using the sasldb or (probably) ldap he will have problems).
I can understand it couldn't be done before since many programs using sasl hadn't been upgraded to sasl v2, but now most (if not all) of them can use the new sasl library.


The latest stable release of openldap (2.1.12) should support cyrus-sasl v2 (according to its README).
I don't know if there are patches around for 2.0.27.


New versions are not allowed to be uploaded until 9.1 is released. Getting 2.1.XX in _properly_ is not realistic. Maybe after 9.1...

Well, as I said the sasl v1 library has been deprecated for more than a year, and for almost the same time (spanning two mandrake releases) I've been uploading to incoming packages for cyrus-sasl v2.

Bye

--
Luca Olivetti
Note.- This message reached you today, it may not tomorrow if you
are using MAPS or other RBL. They arbitrarily 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

Attachment: pgp00000.pgp
Description: PGP signature



Reply via email to