Le samedi, 2 juin 2012 16.56:10, vous avez écrit : > > 2) Handling of the transition > > > > I just tested with a clean user: the current kde-config-gtk-style creates > > one .gtkrc-2.0-kde while your new kde-config-gtk-style creates one > > .gtkrc-2.0-kde4 that is a symlink to .gtkrc-2.0 . You should probably > > cope with > > 04_no_kde4_in_configfile.diff in src:kcm-gtk and make sure any changes > > put there by kcm-gtk is kept gracefully. > > Done.
Sorry, but no. I just tested and it doesn't work. With the attached .gtkrc-2.0-kde as created by the current src:kcm-gtk, when entering the dialog of src:kde-gtk-config, the dialogs don't show "Raleigh" nor "DejaVu Sans 9", but "oxygen-gtk" and "Bitstream Charter 12" (and "Emacs" for the GTK3 theme). That's not what I'd call "any changes there are kept gracefully". I'll upload this package [0] when user changes setup by kde-config-gtk-style 2:0.5.3-1 are kept and converted (if needed) by kde-config-gtk-style 3:2.0-1. That's rather easy to test… Cheers, OdyX [0] But feel free to find another sponsor.
# This file was written by KDE
# You can edit it in the KDE control center, under "GTK Styles and Fonts"
include "/usr/share/themes/Raleigh/gtk-2.0/gtkrc"
style "user-font"
{
font_name="DejaVu Sans"
}
gtk-theme-name="Raleigh"
gtk-font-name="DejaVu Sans 9"
signature.asc
Description: This is a digitally signed message part.
