Comments on: dummy gconfd http://blogs.gnome.org/tthurman/2008/11/19/dummy-gconfd/ Thomas Thurman does not like cold meals because of broken applications. Fri, 30 Oct 2009 10:59:14 +0000 http://wordpress.org/?v=2.8.5.2 hourly 1 By: Alban http://blogs.gnome.org/tthurman/2008/11/19/dummy-gconfd/comment-page-1/#comment-374 Alban Wed, 19 Nov 2008 10:47:25 +0000 http://blogs.gnome.org/tthurman/?p=167#comment-374 Chris Lord> Does it really work? If your config file /etc/gconf/2/path contains include $(ENV_MANDATORY_PATH) you can set the environment variable $MANDATORY_PATH and it should look in the directory $MANDATORY_PATH to store the configuration. (see gconf/gconf-internals.c:741) But I did not manage to get it work correctly. If you do, let me know. Chris Lord> Does it really work?

If your config file /etc/gconf/2/path contains
include $(ENV_MANDATORY_PATH)
you can set the environment variable $MANDATORY_PATH and it should look in the directory $MANDATORY_PATH to store the configuration.
(see gconf/gconf-internals.c:741)

But I did not manage to get it work correctly. If you do, let me know.

]]> By: Chris Lord http://blogs.gnome.org/tthurman/2008/11/19/dummy-gconfd/comment-page-1/#comment-373 Chris Lord Wed, 19 Nov 2008 07:40:40 +0000 http://blogs.gnome.org/tthurman/?p=167#comment-373 If you used gconf-dbus (is this the default yet?), you could change the dbus environment variables, launch another dbus daemon, launch another gconfd that you've built to look in a different prefix, and use that? I think? If you used gconf-dbus (is this the default yet?), you could change the dbus environment variables, launch another dbus daemon, launch another gconfd that you’ve built to look in a different prefix, and use that? I think?

]]>