Remove gsettings-schema-convert tool

Having this tool in GLib is a bad idea for a number of reasons:

  - experience has shown that the simple file format was a bad idea

  - the tool is currently implemented with a hack that would require a
    dependency inversion to solve (the tool needs to depend on Python
    GVariant bindings)

  - the tool itself is unmaintained

It will be moved to the GConf git repository so people can continue to
use it for the purpose of converting GConf schemas.

docs/reference/gio/Makefile.am

@@ -128,7 +128,6 @@ content_files =			\
 	gio-querymodules.xml	\
 	glib-compile-schemas.xml\
 	gsettings.xml		\
-	gsettings-schema-convert.xml \
 	gdbus.xml		\
 	$(NULL)
 
@@ -152,7 +151,6 @@ man_MANS =			\
 	gio-querymodules.1	\
 	glib-compile-schemas.1	\
 	gsettings.1	\
-	gsettings-schema-convert.1 \
 	gdbus.1
 
 if ENABLE_MAN

docs/reference/gio/gio-docs.xml

@@ -174,7 +174,6 @@
         <xi:include href="gio-querymodules.xml"/>
         <xi:include href="gsettings.xml"/>
         <xi:include href="glib-compile-schemas.xml"/>
-        <xi:include href="gsettings-schema-convert.xml"/>
         <xi:include href="gdbus.xml"/>
     </chapter>
   </part>

docs/reference/gio/glib-compile-schemas.xml

@@ -74,12 +74,6 @@ in the future.
 </refsect2>
 </refsect1>
 <refsect1><title>See also</title>
-<para>
-<citerefentry>
-  <refentrytitle>gsettings-schema-convert</refentrytitle>
-  <manvolnum>1</manvolnum>
-</citerefentry> is a utility to convert GConf schemas into GSettings schemas.
-</para>
 </refsect1>
 </refentry>
 

docs/reference/gio/gsettings-schema-convert.xml

@@ -1,113 +0,0 @@
-<refentry id="gsettings-schema-convert" lang="en">
-
-<refmeta>
-  <refentrytitle>gsettings-schema-convert</refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo class="manual">User Commands</refmiscinfo>
-</refmeta>
-
-<refnamediv>
-  <refname>gsettings-schema-convert</refname>
-  <refpurpose>GConf to GSettings schema conversion</refpurpose>
-</refnamediv>
-
-<refsynopsisdiv>
-  <cmdsynopsis>
-    <command>gsettings-schema-convert</command>
-    <arg choice="opt" rep="repeat">option</arg>
-    <arg choice="req">file</arg>
-  </cmdsynopsis>
-</refsynopsisdiv>
-
-<refsect1><title>Description</title>
-<para><command>gsettings-schema-convert</command> converts between GConf
-and GSettings schema file formats. Note that the conversion is not
-expected to be fully automated. You are expected to verify and edit
-the result of the conversion.
-</para>
-<para>
-Note that GSettings schemas need to be converted into binary form
-with <link linkend="glib-compile-schemas">glib-compile-schemas</link> before they
-can be used by applications.
-</para>
-
-<refsect2><title>Options</title>
-<variablelist>
-
-<varlistentry>
-<term><option>-h</option>, <option>--help</option></term>
-<listitem><para>
-Print help and exit
-</para></listitem>
-</varlistentry>
-
-<varlistentry>
-<term><option>-o <replaceable>OUTPUT</replaceable></option>, <option>--output=<replaceable>OUTPUT</replaceable></option></term>
-<listitem><para>
-Store the generated output in the file <replaceable>OUTPUT</replaceable>. If no output file is specified, the generated output is written to stdout.
-</para></listitem>
-</varlistentry>
-
-<varlistentry>
-<term><option>-f</option>, <option>--force</option></term>
-<listitem><para>
-Overwrite the output file if it already exists.
-</para></listitem>
-</varlistentry>
-
-<varlistentry>
-<term><option>-g</option>, <option>--gconf</option></term>
-<listitem><para>
-The input file is a GConf schema.
-</para></listitem>
-</varlistentry>
-
-<varlistentry>
-<term><option>-s</option>, <option>--simple</option></term>
-<listitem><para>
-The input file is a simple GSettings schema. If the input
-format is not explicitly specified, this is the default.
-</para></listitem>
-</varlistentry>
-
-<varlistentry>
-<term><option>-x</option>, <option>--xml</option></term>
-<listitem><para>
-Produce a GSettings schema in XML format. If the output format
-is not explicitly specified, a GConf schema will be converted
-into a simple Gsettings schema, and a simple GSettings schema
-will be converted into XML.
-</para></listitem>
-</varlistentry>
-
-<varlistentry>
-<term><option>-i <replaceable>ID</replaceable></option>, <option>--schema-id=<replaceable>ID</replaceable></option></term>
-<listitem><para>
-Use <replaceable>ID</replaceable> as the schema id in the generated
-GSettings schema.
-</para></listitem>
-</varlistentry>
-
-<varlistentry>
-<term><option>-d <replaceable>DOMAIN</replaceable></option>, <option>--gettext-domain=<replaceable>DOMAIN</replaceable></option></term>
-<listitem><para>
-Use <replaceable>DOMAIN</replaceable> as the gettext domain in the generated
-GSettings schema.
-</para></listitem>
-</varlistentry>
-
-</variablelist>
-</refsect2>
-</refsect1>
-<refsect1><title>See also</title>
-<para>
-<citerefentry>
-  <refentrytitle>gsettings-data-convert</refentrytitle>
-  <manvolnum>1</manvolnum>
-</citerefentry> a related command to migrate user settings
-from GConf to GSettings.
-</para>
-</refsect1>
-
-</refentry>
-

docs/reference/gio/migrating-gconf.xml

@@ -159,7 +159,7 @@
 
       <para>
         If you are porting your application from GConf, most likely you already
-        have a GConf schema. GIO comes with a commandline tool
+        have a GConf schema. GConf comes with a commandline tool
         <link linkend="gsettings-schema-convert">gsettings-schema-convert</link>
         that can help with the task of converting a GConf schema into
         an equivalent GSettings schema. The tool is not perfect and

gio/Makefile.am

@@ -553,7 +553,6 @@ gioenumtypes.c: $(gio_headers) gioenumtypes.c.template
 gio-2.0.lib: libgio-2.0.la gio.def
 	lib -machine:@LIB_EXE_MACHINE_FLAG@ -name:libgio-2.0-$(LT_CURRENT_MINUS_AGE).dll -def:gio.def -out:$@
 
-dist_bin_SCRIPTS = gsettings-schema-convert
 bin_PROGRAMS = gio-querymodules glib-compile-schemas gsettings
 
 gio_querymodules_SOURCES = gio-querymodules.c