Remove 'set lock' support from dconf

The dconf service can not presently be run at the system level and it
doesn't make sense to support locks on user-level databases.  It also
became clear that most distributors and sysadmins would rather work
directly with text files anyway, so we supported that directly instead.

For this reason, 'set lock' support has never been properly implemented.

All the plumbing was added for it though, which means we have it
appearing on the API of the client library and documented in the help of
the commandline tool.  This is misleading, since these functions do
nothing at all (and actually contain bugs anyway since their
do-nothingness was never actually tested).

For now, we rip out these functions.  We can add them back later if we
decide to support this properly.

1 files changed, 0 insertions, 18 deletions

diff --git a/service/service.c b/service/service.c
index 99051ec..407f8a1 100644
--- a/service/service.c
+++ b/service/service.c
@@ -280,24 +280,6 @@ method_call (GDBusConnection       *connection,
       g_free (tag);
     }
 
-  else if (strcmp (method_name, "SetLocked") == 0)
-    {
-      GError *error = NULL;
-      const gchar *name;
-      gboolean locked;
-
-      g_variant_get (parameters, "(&sb)", &name, &locked);
-
-      if (!dconf_writer_set_lock (writer, name, locked, &error))
-        {
-          g_dbus_method_invocation_return_gerror (invocation, error);
-          g_error_free (error);
-          return;
-        }
-
-      g_dbus_method_invocation_return_value (invocation, NULL);
-    }
-
   else
     g_assert_not_reached ();
 }