Le mardi 11 février 2014 à 19:33 -0500, Chris Reffett a écrit : > This doesn't make sense to me at all. I can't see why slotted > libraries can't just use USE flags to specify what toolkit they're > built against, just like any other package in the tree (so, for > example, a package that needs webkit-gtk built against gtk3 would > depend on webkit-gtk[gtk3] instead of webkit-gtk:3). I'm well aware > that there could be limitations I'm unaware of (maybe the package only > can build one at a time?), but this is how it looks to me. By > switching to versioned gtk flags, this kills two birds with one stone: > it makes it obvious to the end user which version they're trying to > build their package against, and it gets rid of the need for (ab)using > revision numbers to implement slots like that. And here comes the "version abuse" troll again. This discussion was settled months ago by exhaustion so please do not try to put some gasoline on it. Most packages we have been confronted to chose to only support gtk2 or gtk3 and if in their history the supported gtk2 then gtk3, we need a slot for that because it makes sense. See gnome-desktop, glade, gtkhtml, at-spi, libgda, gucharmap, vte, etc. For those packages that still support both actively, we still want slots because most packages we have seen (webkit-gtk, gtk-vnc, spice and more that since lost their gtk2 support) only allowed building against one toolkit at a time. -- Gilles Dartiguelongue Gentoo