Recently I did some work for Gnome despite KDE being my primary desktop.

After a nice chat with the Gnome team I bumped gtk+ to 2.10, which uses the new cairo-1.2.0 with many new features. The new gtk+ is hard masked to ensure proper testing of the currently ~arch ebuilds so that they can be marked stable. To get the new gtk+ you have to unmask the new cairo as well as a new glib and pango.
Despite being compatible for applications, gtk+-2.10.0 uses a new directory for the engines and modules. That means you have to rebuild them to work correctly. To inform users about this change I am using the new elog functionality in the postinstall message of gtk+. After updating you can easily rebuild the affected ebuilds using portage-utils:

emerge -va1 $(qfile -qC /usr/lib/gtk-2.0/2.[^1]* )

3 thoughts on “Gtk+-2.10.0”

  1. qfile is from “portage-utils”. Try emerge portage-utils. It can do the following:
    $ qfile
    Usage: qfile : list all pkgs owning files

    Options: -[evqChV]
    -e, –exact * Exact match
    -v, –verbose * Make a lot of noise
    -q, –quiet * Tighter output; suppress warnings
    -C, –nocolor * Don’t output color
    -h, –help * Print this help and exit
    -V, –version * Print version and exit

    like qfile /usr/bin/mplayer will return mplayer.
    Perfect to let it run on the directory in this case!

  2. Just an fyi, this might break on libgnomeui-2.14.x, with an error about gnome-vfs. If this happens, upgrade to libgnome-2.15, by unmasking it. Thanks for the tip! I didn’t realise that /usr/lib/gtk-2.0 still held items from 2.4, and as a result SVG icons and gnome-vfs weren’t working anymore in Xfce. I wish I stumbled across this post before I figured that out the hard way!

Comments are closed.