Comment 7 for bug 524496

@Michael - why don't we use 'gtk-engines2' instead of the port 'gtk2-clearlooks'? AFAIU 'gtk-engines2' contains a maintained version of 'Clearlooks' from gnome.org whereas the sources of the port 'gtk2-clearlooks' from sourceforge.net are no longer updated. The portfile for 'gtk-engines2' appears to get updated with new releases from gnome.org.

This would requires some changes in osx-app.sh since the script explicitly tests for the theme 'Clearlooks-Quicksilver' instead of the engine itself (i.e. fails if the theme engine is installed as part of gtk-engines2). Since we bundle a custom theme anyway there's no need for the theme 'Clearlooks-Quicksilver' itself to be installed in MacPorts.

Note: the ports gtk2-clearlooks and gtk-engines2 can't be active at the same time (results in a conflict because they use the same paths and file names when activated).