[gentoo-dev] Re: RFC: GTK USE flag situation (gtk, gtk2, gtk3; relevant to bug #420493)
On Wed, 12 Feb 2014 09:10:31 +0100 Gilles Dartiguelongue wrote: > 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. Using arbitrary revision numbers to make up for the fact that you can't install multiple SLOTs of the same version of a package is a fucking travesty. -- Ryan Hillpsn: dirtyepic_sk gcc-porting/toolchain/wxwidgets @ gentoo.org 47C3 6D62 4864 0E49 8E9E 7F92 ED38 BD49 957A 8463 signature.asc Description: PGP signature
[gentoo-dev] Re: RFC: GTK USE flag situation (gtk, gtk2, gtk3; relevant to bug #420493)
On Tue, 11 Feb 2014 19:33:06 -0500 Chris Reffett wrote: > 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. Exactly. For wxGTK my options are using a gtk3 USE flag, adding a whole new wxGTK-gtk3 ebuild, or using a 3.0-gtk3 SLOT and some clumsy -r300 thing. The second option brings along a nightmare of file collisions (we have enough trouble supporting multiple installed versions, never mind multiple toolkits within those versions), and the last option isn't actually feasible because everything in the eclass/eselect is tied directly into the SLOT. -- Ryan Hillpsn: dirtyepic_sk gcc-porting/toolchain/wxwidgets @ gentoo.org 47C3 6D62 4864 0E49 8E9E 7F92 ED38 BD49 957A 8463 signature.asc Description: PGP signature
