Unsure if this belongs here (gnome-themes-standard) or against gtk2/gtk3, but as of F15-alpha, the only pkg in the distro that provides /etc/gtk-2.0/gtkrc (and simililarly /etc/gkt-3.0/settings.ini) is gnome-themes-standard which is not a required dependendency for gtk2, gtk3 respectively.
So, systems without gnome-themes-standard installed, like any non-gnome spin, end up with ugly anaconda, firstboot (and others possibly).
Options off the top of my head (not necessarily mutually exclusive):
1. gtk2, gtk3 packages include dependencies on *something* that provides a default/sane /etc/gtk-2.0/gtkrc and /etc/gtk-3.0/settings.ini, respectively
2. provide some mechanism to be able to switch system gtk theming defaults that doesn't involve file/pkg conflicts
3. <insert better idea here>
And dragging in gnome-themes-standard as is is not a good idea because that drags in several unwanted dependencies which are not required for GTK+ to work.
Created attachment 486339 [details]
Would the attached patch to the specfile be an acceptable solution?
This moves the GTK+ config files to the GTK+ theme subpackages. Those subpackages are required by gnome-themes-standard, so any installs which get the config files now will still get them dragged in. But with the change, it is enough to ship adwaita-gtk3-theme on a spin to get GTK+ 3 Adwaita-themed.
(FWIW, the gtk-icon-theme-name, gtk-button-images and gtk-menu-images settings should be mostly irrelevant, they will most likely get overridden through xsettings anyway, at least xsettings-kde does that. Only places like firstboot see them at all.)
As a result of bug 675509 the theme was split similar to Kevin's proposal, so I wonder if this is still a problem.
Yes. Check my patch in my proposal carefully, it is a followup to the changes from bug #675509. It moves the default GTK+ config files into the adwaita-gtk-theme subpackages introduced by the fix for bug #675509.
Ping? Is the specfile patch I attached in comment #2 acceptable?
gnome-themes-standard-2.91.93-2.fc15 has been submitted as an update for Fedora 15.
This "fix" is very wrong!
Dragging in gnome-themes-standard from adwaita-cursor-theme defeats the very purpose of the adwaita-cursor-theme split. This is not acceptable.
See also the discussion in bug 675509.
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing gnome-themes-standard-2.91.93-3.fc15'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
Uh no, gnome-themes-standard-2.91.93-3.fc15 doesn't fix this issue. (The broken "fix" got reverted, but no working one was applied.)
What do you think of my suggested fix from comment #2?
Kevin, now you're mistaken; your patch was applied indeed. See the spec file at http://pkgs.fedoraproject.org/gitweb/?p=gnome-themes-standard.git;a=tree;h=refs/heads/f15/master;hb=refs/heads/f15/master
Oh, indeed it's there, I still can't find the commit that made the change, but it's there. :-)
But you will have to file a new update request because the one you edited got unpushed due to bad karma.
This is the relevant commit: http://pkgs.fedoraproject.org/gitweb/?p=gnome-themes-standard.git;a=blobdiff;f=gnome-themes-standard.spec;h=a4382263ab60c632a4b173d02187849dca2a8c2a;hp=fbf2177fa8393e6d494cde9e2d21fb9b4b8a677b;hb=909eb90ccc4dfeb4cc5b44dfe1fb6b71f8984b3f;hpb=92edc63ef63f669b2dc55afde0eeadd19a5eb9a4
Filing a new update now.
gnome-themes-standard-3.0.0-1.fc15, which includes this fix (among other things) got pushed to F15 stable today and will be included in the F15 Beta.