Default to session autostart instead of DBus (Fixes #27)

Previously notifyd was started over DBus when the first notification got
sent, so in theory it could refrain from running during the whole
session if no notifications were sent.

This behavior is sort of nice, but has a few backdraws.
1) The first notification may show up a little laggy because of starting
up the daemon.
2) Other notification services (e.g. KDE's) may be started ahead of
notifyd and occupy the DBus name, hindering notifyd from starting up so
users may end up not seeing notifications.

configure.ac.in

@@ -110,8 +110,8 @@ AM_CONDITIONAL([USE_OLD_GET_SERVER_INFORMATION_SIGNATURE],
 dnl dbus start daemon
 AC_ARG_ENABLE([dbus-start-daemon],
               [AS_HELP_STRING([--enable-dbus-start-daemon],
-                              [Start daemon by dbus - if not set by autostart. (default=yes)])],
-              [use_dbus_start_daemon=$enableval], [use_dbus_start_daemon=yes])
+                              [Start daemon via DBus instead of regular session autostart. (default=no)])],
+              [use_dbus_start_daemon=$enableval], [use_dbus_start_daemon=no])
 AM_CONDITIONAL([USE_DBUS_START_DAEMON],
                [test "x$use_dbus_start_daemon" = "xyes"])
 
@@ -135,3 +135,18 @@ AC_OUTPUT(
     panel-plugin/Makefile
     po/Makefile.in
 ])
+
+dnl ***************************
+dnl *** Print configuration ***
+dnl ***************************
+echo
+echo "Build Configuration:"
+echo
+echo "* Installation prefix:       $libdir"
+echo "* Debug Support:             $enable_debug"
+if test "x$use_dbus_start_daemon" = "xyes"; then
+echo "* Startup method:            DBus"
+else
+echo "* Startup method:            Autostart"
+fi
+echo