pidgin: bb87bb7d: Clean up the comments about MSNP14, and ...

[nosnilmot at pidgin.im]

-----------------------------------------------------------------
Revision: bb87bb7d79b90e03008fa67a09a941492a582312
Ancestor: c288d0643553d34e59fdea43517c6eb2cd40852d
Author: nosnilmot at pidgin.im
Date: 2008-05-14T01:57:45
Branch: im.pidgin.pidgin
URL: http://d.pidgin.im/viewmtn/revision/info/bb87bb7d79b90e03008fa67a09a941492a582312

Modified files:
        configure.ac

ChangeLog: 

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)

-------------- next part --------------
============================================================
--- configure.ac	c23f8410d2355c1a0e091cca430117b27f4aceef
+++ configure.ac	c23ca72d817a5148f7ef70ab24268ab3a854fc5e
@@ -948,9 +948,8 @@ AC_SUBST(GADU_CFLAGS)
 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")