# HG changeset patch
# User Stu Tomlinson <stu@nosnilmot.com>
# Date 1210730265 0
# Node ID d464485a2bfc67b7b4d1d1a4c13ba81246f99fcc
# Parent  09cab27cbe42f2b50a70edf53282a851c9ed79c8
Clean up the comments about MSNP14, and make the --enable-msnp14 option no
longer commented out.
This makes it possible, with stock pidgin, to build with msnp14 using
--enable-msnp14 - are we ready for this? (my thought being that if we are
ready for this we can see what happens when "early adopters" turn it on and
maybe, just maybe, making msnp14 default for 2.5.0)

diff -r 09cab27cbe42 -r d464485a2bfc configure.ac
--- a/configure.ac	Tue May 13 20:54:30 2008 +0000
+++ b/configure.ac	Wed May 14 01:57:45 2008 +0000
@@ -948,9 +948,8 @@
 AC_SUBST(GADU_LIBS)
 AC_SUBST(GADU_CFLAGS)
 
-# uncomment the next line to make MSNP14 the available
-# AC_ARG_ENABLE(msnp14,[AC_HELP_STRING([--enable-msnp14], [Disable the newer MSNP14 protocol])],,enable_msnp14=no)
-enable_msnp14=no
+# change the next line to make MSNP14 the default (s/enable/disable/; s/no/yes/;)
+AC_ARG_ENABLE(msnp14,[AC_HELP_STRING([--enable-msnp14], [Enable the newer MSNP14 protocol (unsupported)])],,enable_msnp14=no)
 
 AC_ARG_ENABLE(distrib,,,enable_distrib=no)
 AM_CONDITIONAL(DISTRIB, test "x$enable_distrib" = "xyes")