Allow cyrus-sasl2 & postfix users to use Berkeley DB 4.3 Fix: Apply these patches. % diff -u /usr/ports/security/cyrus-sasl2/Makefile.orig /usr/ports/security/cyrus-sasl2/Makefile % diff -u /usr/ports/security/cyrus-sasl2-saslauthd/Makefile.orig /usr/ports/security/cyrus-sasl2-saslauthd/Makefile % diff -u /usr/ports/mail/postfix/scripts/configure.postfix.orig /usr/ports/mail/postfix/scripts/configure.postfix
Responsible Changed From-To: freebsd-ports-bugs->ume Over to the maintainer of two of the three ports listed herein. To the submitter: including patches for multiple ports in the same PR creates a sort of dilemma for us as we try to figure out who to hand the PR off to. If, in the future, you could separate them somewhat (e.g. by maintainer), this would make things easier. Also, Cc:ing the maintainers would also be helpful. http://www.freebsd.org/cgi/query-pr.cgi?pr=76154 Adding to audit trail from misfiled PR ports/76255: Date: Sat, 15 Jan 2005 05:47:13 +0900
Yes, both cyrus-sasl and cyrus-imap22 both work, when "forced to" compile with db4.3. Very little forcing is needed, especially for the cyrus-imap22, which was more recently released. But the db-backends CAN NOT be mixed -- imap must use the same one, that sasl is using. -mi
Responsible Changed From-To: ume->ports Thanks! I've just committed cyrus-sasl2 part. However, I'm not using postfix. So, please someone take care of the rest.
Responsible Changed From-To: ports->freebsd-ports-bugs Canonicalize assignment.
State Changed From-To: open->closed Committed, thanks!