[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

gconf changes



gconf proposal
==============

This proposal attempts to solve a number of problems:

1) Schemas provided by applications are not intended to be editted.
2) Schemas are registered as packages are installed, so should be kept
in /var/lib/gconf
3) We should not alter upstream's packages to Debianise them
4) We need to be able to have Debian branding
5) CDDs may want to have further branding
6) A sysadmin may want to further customise the systems.

We've chatted about this a bunch on #gnome-debian, and I've assembled a
path file that I think meets all the needs and a few FIXMEs.  Flame
away...


# Sysadmin forced settings
xml:readonly:/etc/gconf/gconf.xml.defaults

# Local Forced settings (Packaged)
xml:readonly:/usr/share/gconf/local-optional

# Sabayon mandatory FIXME - Is this the right path?  How is it made
mandatory?
include "$(HOME)/.gconf.path.mandatory"

# User Preferences

# Now see where users want us to look - basically the user can stick
arbitrary
# sources in a ~/.gconf.path file and they're inserted here
include "$(HOME)/.gconf.path"

# Give users a default storage location, ~/.gconf
xml:readwrite:$(HOME)/.gconf

# Sabayon optional FIXME - Is this the right path?  Shouldn't this be
system-wide?
include "$(HOME)/.gconf.path.defaults"

# Local Branding (Packaged)
xml:readonly:/usr/share/gconf/local-optional

# CDD Branding
xml:readonly:/usr/share/gconf/cdd

# Debian branding
xml:readonly:/usr/share/gconf/debian

# Application default
xml:readonly:/var/lib/gconf/



Reply to: