CCing shres :p

Well, if the system does not have network manager installed then the network manager support isn't built anyway. Adding a --with-nmsupport should be trivial but this is still not a run time check. 

When i wrote this it was decided to make this not a turn off'able feature. Which is why it wasnt a plugin. A run time check is rather unnecessary anyway, I am open to people convincing me otherwise. 

I have problems every now and then with building Evolution due to the networkmanager libraries which are from my system (rather than from a build environment). These libraries pull other system (read: old) libraries which make my linker die.

So I work around this issue with this patch, maybe it's useful for anyone.

Index: configure.in
===================================================================
--- configure.in	(revision 34030)
+++ configure.in	(working copy)
@@ -1412,12 +1412,12 @@ dnl --- evolution (shell) flags
 
 NM_SUPPORT_PACKAGES=""
 
-PKG_CHECK_MODULES(NM, dbus-glib-1 libnm_glib, NM_SUPPORT_GLIB="yes", NM_SUPPORT_GLIB="no")
+PKG_CHECK_MODULES(NM, dbus-glib-1 libnm_glib, NM_SUPPORT_GLIB="no", NM_SUPPORT_GLIB="no")
 if test "x$NM_SUPPORT_GLIB" = "xyes"; then 
    AC_DEFINE(NM_SUPPORT_GLIB, 1, [network manager available])
    NM_SUPPORT_PACKAGES="dbus-1 dbus-glib-1 libnm_glib"
 else
-   PKG_CHECK_MODULES(NM, dbus-glib-1, NM_SUPPORT="yes", NM_SUPPORT="no")
+   PKG_CHECK_MODULES(NM, dbus-glib-1, NM_SUPPORT="no", NM_SUPPORT="no")
    AC_CHECK_HEADER(NetworkManager/NetworkManager.h, [ nm_header="yes" ] )
    if test "x$NM_SUPPORT" = "xyes" -a "x$nm_header" = "xyes"; then 
 	AC_DEFINE(NM_SUPPORT, 1, [network manager available])
@@ -1426,9 +1426,11 @@ else
         NM_SUPPORT=no
    fi	   
 fi 
-
+        
 AM_CONDITIONAL(NM_SUPPORT_GLIB, test x$NM_SUPPORT_GLIB = xyes)
 AM_CONDITIONAL(NM_SUPPORT, test x$NM_SUPPORT = xyes)
+NM_SUPPORT=no
+NM_SUPPORTED_PACKAGES=""
 
 
 EVO_SET_COMPILE_FLAGS(SHELL, libgnomeui-2.0 libbonoboui-2.0 libglade-2.0 gnome-vfs-2.0 libgtkhtml-$GTKHTML_PACKAGE $NM_SUPPORT_PACKAGES)  


PS: A configure switch would be appreciated ;-) 

Bumping version to a stable release.

I agree with shres.  Closing based on comment #2.

Well Matthew, as I told in comment #3, it actually is useful to disable nm on a configure basis, although I think it's more or less a cornercase. But still, it would save other poeples time, if they could just switch nm-support off.

Right now, I do need that flag because I can't build evo due to new functions introduced in glib.
JHbuild pulls networkmanager libs from my system which in turn pull my systems glib which make Evo not being build.If such a flag existed and worked properly, I would be able to build Evo without the need to find an uptodate NetworkManager.

So I am reopening this as I have brought up reasons which might be convincing to implement that.

We have an --enable-nm option now.  Note that NetworkManager integration is enabled by default and configure aborts if it can't find a NetworkManager package.  If you don't want NetworkManager integration you have to be explicit about it.

Closing as fixed.