dev-libs/cyrus-sasl-2.1.19 released. http://asg.web.cmu.edu/archive/message.php?mailbox=archive.cyrus-sasl&msg=5954 Good news for those still using pam_mysql. [quote]I am pleased to announce the release of Cyrus SASL 2.1.19 on ftp.andrew.cmu.edu. This release contains a large number of bugfixes and cleanups from the last version, including the "-r" option for saslauthd to instruct it to reassemble realm and username into a username of "user@realm" form. There is now also support for passing of GSSAPI credentials, and support for SQLite in the SQL auxprop plugin. Please send feedback to cyrus-sasl@lists.andrew.cmu.edu or cyrus-bugs@andrew.cmu.edu (private list). Download at: ftp://ftp.andrew.cmu.edu/pub/cyrus-mail/cyrus-sasl-2.1.19.tar.gz or http://ftp.andrew.cmu.edu/pub/cyrus-mail/cyrus-sasl-2.1.19.tar.gz - -Rob [/quote]
ready to test.
Whentrying to install this ebuild I get: merc root # emerge -uD cyrus-sasl Calculating dependencies ...done! >>> emerge (1 of 1) dev-libs/cyrus-sasl-2.1.19 to / >>> md5 src_uri ;-) cyrus-sasl-2.1.19.tar.gz gdbm berkdb * You have both "gdbm" and "berkdb" in your USE flags. * please choose only one for your SASLdb database backend. * It would be best practice to add the set of USE flags that you use for this * package to the file: /etc/portage/package.use. Example: * `echo "dev-libs/cyrus-sasl gdbm -berkdb" >> /etc/portage/package.use` * to build cyrus-sasl with GNU database as your SASLdb backend. Ok that's understanable, BUT there is no such file as '/etc/portage/package.use'?
> BUT there is no such file as '/etc/portage/package.use'? Just create one. # mkdir /etc/portage; echo "dev-libs/cyrus-sasl gdbm -berkdb" >> /etc/portage/package.use `man 5 portage` for more info.
