Bug#310065: fixed in gconf2 2.10.1-2
Loïc Minier
lool at dooz.org
Sat Oct 7 22:01:59 CEST 2006
reopen 310065
retitle 310065 Overrides for GConf path
stop
Hi,
Josselin, I had a fairly long conversation with the submitter, and I
think the changes you've introduced are not sufficient for his needs:
> * Customize the default path file, which now:
> - allows to set defaults or mandatory settings in packages;
> - sets a place for autogenerated defaults in /var/lib;
> - reads user customization files for Sabayon.
> (closes: #310065).
This is mainly aimed at setting defaults on a per-package basis, not
pathes I think.
The submitter maintains a package named desktop-profiles which permits
using different criterias to decide upon login what configuration to
use. For example, you can make people in the group "teachers" use the
gconf defaults for teachers, and force "students" to have some
mandatory gconf settings. This is determined dynamically (by running
some commands for example), and relies on GConf trickery to work
(include $(ENV_MANDATORY_PATH) and include $(ENV_DEFAULTS_PATH)).
One advantage of desktop-profiles over -- say -- GConf is that it is
aware of multiple desktop environments, so CDD have a single entry
point (/etc/desktop-profiles/desktop-profiles.listing) to insert GConf
data sources or KDE preferences sources, or whatever (it handles Rox
stuff, Gnustep stuff, and XDG/Freedesktop stuff too).
The tool relies on changing the GConf path, and will generate an
additional GConf path on each login based on the result of commands and
group checks.
I think the extensibility of the GConf path would be useful for more
things that I imaginated now that I look at the default path, we could
have a /etc/gconf/2/path.d with:
10_local-mandatory.path:
xml:readonly:/etc/gconf/gconf.xml.mandatory
(we could symlink instead of "include /etc/gconf/2/local-mandatory.path")
30_user-sources
include "$(HOME)/.gconf.path"
(we could symlink instead of "include /etc/gconf/2/local-defaults.path")
50_local-defaults.path:
xml:readonly:/etc/gconf/gconf.xml.defaults
60_debian-defaults.path:
xml:readonly:/var/lib/gconf/debian.defaults
70_apps-defaults.path:
xml:readonly:/var/lib/gconf/defaults
and sabayon would ship:
20_sabayon-mandatory.path:
include "$(HOME)/.gconf.path.mandatory"
40_sabayon-optional.path:
include "$(HOME)/.gconf.path.defaults"
and desktop-profiles would ship:
25_desktop-profiles-mandatory.path:
include $(ENV_MANDATORY_PATH)
45_desktop-profiles-optional.path:
include $(ENV_DEFAULTS_PATH)
Perhaps this is oversplit and we could live with only splitting out
sabayon and desktop-profiles though, which would be my personal
preference.
What do you think?
--
Loïc Minier <lool at dooz.org>
More information about the Pkg-gnome-maintainers
mailing list