On Sat, 2003-11-22 at 03:40, Spider wrote: <snip> In short it is like this :
USE="gtk gtk2" Use gtk+ UI if available (this might be gtk+-1 or gtk+-2, depending on the application & version), if there's both gtk+-1 and gtk+-2 UIs in the package build the gtk+-2 UI. USE="gtk -gtk2" Use gtk+ UI if available (this might be gtk+-1 or gtk+-2, depending on the application & version), if there's both a gtk+-1 and gtk+-2 UIs in the package build the gtk+-1 UI. USE="-gtk -gtk2" Always disable optional gtk+ UI support (doesn't matter if it's gtk+-1 or gtk+-2). USE="-gtk gtk2" Illegal for builds that have an optional gtk+-1 or gtk+-2 UI. 'gtk2' is a qualifier for 'gtk' and should have no effect in this case, the gtk+ UI building has been disabled with '-gtk'. This logic is flawed in quite a few ebuilds and this combination results in undefined behaviour and should be fixed. Could be considered legal for builds that have a non-optional gtk+-1 or gtk+-2 gui. Although in this case for simplicity and consistency sake i would suggest we just default to the most mature and/or recent one of the UIs and make it use the 'gtk' USE flag only. In time we should be able to phase out the gtk2 USE flag altogether (it was meant as a short transition flag). The gtk/gtk2 USE flag combination has been a source of confusion over time, in retrospect this may not have been the best solution to the mixed packages problem at the time (both gtk+1 and gtk+-2 UIs in one package). It worked sufficiently up to now and changing it would probably more trouble than that would be gained from it. In a future similar case this would most likely be done in a different way. For now i suggest devs trying to fix their ebuild's gtk/gtk2 handling to contact one of the gnome devs to work out the best fix. - foser -- [EMAIL PROTECTED] mailing list
