aboutsummaryrefslogtreecommitdiff
path: root/UPDATING
diff options
context:
space:
mode:
authorXin LI <delphij@FreeBSD.org>2012-12-12 20:09:55 +0000
committerXin LI <delphij@FreeBSD.org>2012-12-12 20:09:55 +0000
commita571c07ffb6b542509a8577e85945cae63c45cbe (patch)
treec6a78db7a32a926420377b70b46b2f05c9598e45 /UPDATING
parent6ddf03ddfb9cb7a45e11686c82df230763a2a212 (diff)
downloadports-a571c07ffb6b542509a8577e85945cae63c45cbe.tar.gz
ports-a571c07ffb6b542509a8577e85945cae63c45cbe.zip
Notes
Diffstat (limited to 'UPDATING')
-rw-r--r--UPDATING17
1 files changed, 17 insertions, 0 deletions
diff --git a/UPDATING b/UPDATING
index d28097570381..cb2dc1b406fb 100644
--- a/UPDATING
+++ b/UPDATING
@@ -6,6 +6,23 @@ You should get into the habit of checking this file for changes each time
you update your ports collection, before attempting any port upgrades.
20121212:
+ AFFECTS: users of openldap24-client who uses SASL
+ AUTHOR: Xin Li <delphij@FreeBSD.org>
+
+ There is a change in the openldap24-client port which removes the SASL
+ option. If the user previously install openldap24-client, but enabled
+ SASL from the config menu, the user would have to replace it with
+ openldap24-sasl-client.
+
+ Note that this only affects those who manually set SASL from the menu,
+ most of the users are not affected.
+
+ If you use portmaster:
+ portmaster -o net/openldap24-sasl-client openldap24-client
+ If you use portupgrade:
+ portupgrade -fo net/openldap24-sasl-client openldap24-client
+
+20121212:
AFFECTS: users of horde-* applications
AUTHOR: Martin Matuska <mm@FreeBSD.org>