File gksu-gsettings.patch of Package gksu

Only in a: aclocal.m4
--- a/configure.ac
+++ b/configure.ac
@@ -40,8 +40,7 @@ fi
 
 AC_SUBST(HTML_DIR)
 
-AC_PATH_PROG(GCONFTOOL, gconftool-2)
-AM_GCONF_SOURCE_2
+GLIB_GSETTINGS
 
 PKG_CHECK_MODULES(GKSU, [libgksu2 >= 2.0.8, gtk+-2.0 >= 2.4.0])
 
Only in a: gksu-migrate-conf.sh
--- a/Makefile.am
+++ b/Makefile.am
@@ -17,7 +17,4 @@ desktop_in_files = gksu.desktop.in
 dist_desktop_DATA = $(desktop_in_files:.desktop.in=.desktop)
 @INTLTOOL_DESKTOP_RULE@
 
-scriptsdir = $(datadir)/gksu
-dist_scripts_DATA = gksu-migrate-conf.sh
-
 EXTRA_DIST = config.rpath intltool-extract.in intltool-merge.in intltool-update.in
--- a/man/gksu.1
+++ b/man/gksu.1
@@ -23,8 +23,8 @@ su directly.
 Notice that all the magic is done by the underlying library,
 libgksu. Also notice that the library will decide if it should use su
 or sudo as backend using the
-.B /apps/gksu/sudo-mode
-gconf key, if you call the
+.B org.gksu sudo-mode
+gsettings key, if you call the
 .B gksu
 command. You can force the backend by using the
 .B gksudo
--- a/README
+++ b/README
@@ -8,10 +8,7 @@ GKSu is hosted at Savannah! Check http:/
 
 If you're upgrading from a version lower than 1.3.2, you might have
 used the /etc/gksu.conf file to setup gksu's behavior. From that version
-on gksu uses gconf for its configuration. There's a script called
-gksu-migrate-conf.sh which can be used to setup the gconf system according
-to your old config file setup. Just run it with the configuration file
-as its first argument.
+on gksu uses gsettings for its configuration.
 
 The script will be located in ${datadir}/gksu. On 'usual' instalations
 that would be /usr/share/gksu or /usr/local/share/gksu.