currently the gtk+-2.2.1 compile breaks for some ppc users. if a user has xft2 installed, but pango < 1.1.3, the gtk+ compile breaks. 2 things are going on here. 1) the gtk+ script is behaving badly and i've filed a bug: 2) gtk+ ebuilds that depend on xft, are being too lenient w/ pango requirements. the gtk+-2.2.1 ebuild should require >=pango-1.1.3 to avoid hitting the problem #1 above. ppc users are hitting this because everything >pango-1.0.5 is masked ~ppc. and a simple ACCEPT_KEYWORDS="~ppc" emerge -p gtk+ breaks. (ACCEPT_KEYWOPRDS="~ppc" emerge -up gtk+ would have pulled pango-1.2.1.) thoughts?
well it should be possible to use gtk+-2.2 with pango 1.0, but i guess upping that requirement won't hurt. Go ahead and do it. What is the diff between 1 and 2 exactly ? Why is pango 1.2 masked on ppc ? If you unmask gnome it depends on the latest atk/gtk+/glib/pango.
the problem is with gtk+'s configure script as i noted. i'm sure it does work with pango-1.0, but _not_ if you have xft-2 installed. i realize the pango-1.1.3 isn't a hard requirement for gtk+, but it is if you want to avoid this bug: http://bugzilla.gnome.org/show_bug.cgi?id=105692
oh right, ive seen that before with gnome-terminal or something. Nah, upping the dep is ok with me, to be on the safe side.
nall fixed this yet ?
this is in cvs.
