FS#14252 - [kdebase-workspace] rewrites Xsetup
Attached to Project:
Arch Linux
Opened by David Sulaiman (suli) - Wednesday, 15 April 2009, 11:30 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Friday, 05 April 2013, 09:10 GMT
Opened by David Sulaiman (suli) - Wednesday, 15 April 2009, 11:30 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Friday, 05 April 2013, 09:10 GMT
|
Details
Description:
instalation of package kdebase-workspace 4.2.2-3 rewrites /usr/share/config/kdm/Xsetup Additional info: * package version(s) * config and/or log files etc. Steps to reproduce: yaourt -S kdebase-workspace |
This task depends upon
Closed by Sven-Hendrik Haase (Svenstaro)
Friday, 05 April 2013, 09:10 GMT
Reason for closing: Upstream
Additional comments about closing: There's nothing we can do about this at this point except for patching the source code. We can wait and hope this gets backported to kde 4 rather soon.
Friday, 05 April 2013, 09:10 GMT
Reason for closing: Upstream
Additional comments about closing: There's nothing we can do about this at this point except for patching the source code. We can wait and hope this gets backported to kde 4 rather soon.
What do you think about? Should we add kmd/Xsetup and others files to backup array?
If we put every file in the backup array updates are more "complicated"; e.g. Xsession includes a lot more than just some configuration options. So users would have to check a lot of files on every update and compare them to the .pacnew ones.
We should have a look at this (how do others handle this?). As mentioned above it would be best to let the user override default configs in /etc.
The location of the kdm configuration files is not ideal.
Fedora and Slackware create a symlink to /etc/kde/
https://bugs.kde.org/show_bug.cgi?id=194764
https://bugs.kde.org/show_bug.cgi?id=300997