summaryrefslogtreecommitdiff
path: root/engine/dconf-engine.h
diff options
context:
space:
mode:
authorRyan Lortie <desrt@desrt.ca>2011-09-11 12:44:36 -0400
committerRyan Lortie <desrt@desrt.ca>2011-09-11 12:44:36 -0400
commit83e61fdbe0b71bc20c82789b56c48e6dcd44981a (patch)
tree1493eeb8cf53739d4ea657a52308d80776b62be9 /engine/dconf-engine.h
parent8f9f2b5ebd55164985c8330d33d0f8269da4a1c8 (diff)
downloaddconf-83e61fdbe0b71bc20c82789b56c48e6dcd44981a.tar.gz
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.
Diffstat (limited to 'engine/dconf-engine.h')
-rw-r--r--engine/dconf-engine.h6
1 files changed, 0 insertions, 6 deletions
diff --git a/engine/dconf-engine.h b/engine/dconf-engine.h
index 0bde8f0..98333fb 100644
--- a/engine/dconf-engine.h
+++ b/engine/dconf-engine.h
@@ -150,12 +150,6 @@ gboolean dconf_engine_decode_writability_notify (const g
GVariant *body);
G_GNUC_INTERNAL
-void dconf_engine_set_locked (DConfEngine *engine,
- const gchar *path,
- gboolean locked,
- DConfEngineMessage *message);
-
-G_GNUC_INTERNAL
gboolean dconf_engine_interpret_reply (DConfEngineMessage *message,
const gchar *sender,
GVariant *body,