Le lundi 14 novembre 2005 à 09:28 +0100, Jean-Christophe Dubacq a écrit : > It would be marvelous (and probably more FHS compliant) if those > files were not to be dropped in /usr/share/gconf/defaults, but in / > etc/gconf/defaults. > Or better (I do not know how you perceive the whole thing) if your > update-gconf-defaults script could read both in /usr/share/gconf/ > defaults and /etc/gconf/defaults. The /etc/gconf/defaults would be > empty and filled only with localadmin-written stuff (btw, this name > just came as the first off the top of my mind, but could be changed > to /etc/gconf/local-defaults if this helps with transition from older > setups).
All of this is easy to achieve, but the reasoning behind choosing /usr/share/gconf/defaults was to provide a framework for packages, not for system administrators. The recommended way to set local defaults is still to use gconftool or gconf-editor to set them in /etc/gconf/gconf.xml.defaults. These defaults still supersede packaged defaults in /usr/share/gconf/defaults. I don't like to provide 2 ways to do the same thing, especially if it means to diverge from upstream's documentation. Regards, -- .''`. Josselin Mouette /\./\ : :' : [EMAIL PROTECTED] `. `' [EMAIL PROTECTED] `- Debian GNU/Linux -- The power of freedom
