On Fri, Feb 20, 2004 at 12:21:49AM +0100, Achim Bohnet wrote: > Unfortunately that's no solution (IMHO). First time KDE users would have > an empty /etc/kde3 and therefore even installing, e.g., and Xservers > file in /etc/kde3/kdm does not help because kdmrc explicitely > refers to Xservers in /usr/share/config/kdm. Second: to customize > things one would have to do a cp /usr/share/config/<whatever> /etc/kde3/ > and the edit it. Aren't we here in trouble with policy?! Yes, fixing kdm to use kde-config may take a bit of work. Most of the "config" files in /etc/kde3 were not really meant to be user modified. And yes I know KDE is a huge mess upstream, it has slowly been getting cleaned up. In another 10 years it might be as cleaned up as Gnome is today. > AFAIU only reason for dpkg not to install a config file is when > the old and new pkg had the config file but the config file does > not exist when a pkg was updated. But then the apps did also > not work before the update. I don't know what causes it, but it seems to happen fairly frequently. And until I made the patch in 3.2.0-0pre1v1 to look at both locations the config files hadn't moved in a very long time. So I really doubt it was a case of disappearing/reappearing config files in the KDE debs themselves. > So either dpkg has a not yet reported RC bug or KDE upgrade > is broken. Anyone recall another reason dpkg does not install > a config file beside the one I described above? It would seem to be a bug in dpkg, at least afaict. But from what I've read of dpkg people stay as far away as possible from its code. Chris
Attachment:
signature.asc
Description: Digital signature