| 1 |
On Tue, 11 Feb 2014 19:33:06 -0500 |
| 2 |
Chris Reffett <creffett@g.o> wrote: |
| 3 |
|
| 4 |
> This doesn't make sense to me at all. I can't see why slotted |
| 5 |
> libraries can't just use USE flags to specify what toolkit they're |
| 6 |
> built against, just like any other package in the tree (so, for |
| 7 |
> example, a package that needs webkit-gtk built against gtk3 would |
| 8 |
> depend on webkit-gtk[gtk3] instead of webkit-gtk:3). I'm well aware |
| 9 |
> that there could be limitations I'm unaware of (maybe the package only |
| 10 |
> can build one at a time?), but this is how it looks to me. By |
| 11 |
> switching to versioned gtk flags, this kills two birds with one stone: |
| 12 |
> it makes it obvious to the end user which version they're trying to |
| 13 |
> build their package against, and it gets rid of the need for (ab)using |
| 14 |
> revision numbers to implement slots like that. |
| 15 |
|
| 16 |
Exactly. For wxGTK my options are using a gtk3 USE flag, adding a whole new |
| 17 |
wxGTK-gtk3 ebuild, or using a 3.0-gtk3 SLOT and some clumsy -r300 thing. |
| 18 |
The second option brings along a nightmare of file collisions (we have enough |
| 19 |
trouble supporting multiple installed versions, never mind multiple toolkits |
| 20 |
within those versions), and the last option isn't actually feasible because |
| 21 |
everything in the eclass/eselect is tied directly into the SLOT. |
| 22 |
|
| 23 |
|
| 24 |
-- |
| 25 |
Ryan Hill psn: dirtyepic_sk |
| 26 |
gcc-porting/toolchain/wxwidgets @ gentoo.org |
| 27 |
|
| 28 |
47C3 6D62 4864 0E49 8E9E 7F92 ED38 BD49 957A 8463 |
Archives