Bill Allombert writes: > What you need is a 3-way overriding process like Debian menu does:
> 1: ~/.kde3/share/config for user config. 2: /etc/kde3 for sysadmin > config. 3: /use/share/kde3/config for package config. > Files in 1) override files in 2) and 3), files in 2) override files > in 3). > You ship 2) basically empty (everything should go in 3).) > e.g. menu use 1: ~/.menu 2: /etc/menu 3: /usr/lib/menu Hi all, I think this bug touches on a general problem with KDE and the location of its config files. I have looked around a bit, and I would like to propose the following changes: Set kde_confdir to "$kde_prefix/share/config" in admin/debianrules, to make sure applications install their local "config" data in /usr, where it is treated as the default data, as it should. Add /etc/kde3 to the dir_config list of dirs in /etc/kderc. That way, the system administrator can override the default package settings by adding the relevant file to /etc/kde3 and overriding the settings concerned ( read more about the way overriding of settings works in KDE here [1] ). I think this implements the structure suggested in the above bug report, and also matches better with what the KDE KIOSK system expects, so it will become easier for sysadmins to lockdown their system using the KIOSK system. I'd like to hear your thoughts on this, please reply on the debian-qt-kde list, as I think that's where the discussion belongs. cheers domi Footnotes: [1] http://webcvs.kde.org/cgi-bin/cvsweb.cgi/kdelibs/kdecore/README.kiosk?rev=1.44&content-type=text/x-cvsweb-markup