1 |
On Thu, 20 Feb 2014 05:16:55 -0500 |
2 |
Alexandre Rostovtsev <tetromino@g.o> wrote: |
3 |
|
4 |
> The other unfortunate aspect of the gtk3 flag is that it encourages |
5 |
> using flags instead of slotting for libraries that can support both gtk |
6 |
> and gtk3, resulting in needless rebuilds of when one of the flags is |
7 |
> switched on/off. But again, that could be addressed with a bit of |
8 |
> documentation. |
9 |
|
10 |
Slotting a library by toolkit rather than by version just doesn't work in a lot |
11 |
of cases. Having multiple versions of a library installed is common enough |
12 |
practice and upstreams will often take that into account and version their |
13 |
library names, include paths, pkgconfig files, etc. Most don't do that for |
14 |
different toolkits. So if you're slotting by toolkit you have to start |
15 |
installing one in a non-standard location to prevent file collisions (and it's |
16 |
always the newer toolkit since you don't want to break existing packages), and |
17 |
every new ebuild using that toolkit needs to be changed to look in the right |
18 |
place, and you have to start futzing around with symlinks, and wrapper scripts, |
19 |
and eselect, and eclasses, and every time some dev uses the wrong depend atom |
20 |
you get a bug about it, and it goes on and on and on. |
21 |
|
22 |
Or you can add USE=gtk3, deal with collisions internally, install one set of |
23 |
headers, and go do something productive with your life. |
24 |
|
25 |
wxGTK not only splits up libraries by version and toolkit, but also by charset |
26 |
and debug/release. If we had to use different SLOTs rather than USE flags we |
27 |
would need eight of them for 2.8 alone. And I don't know how we would name the |
28 |
ebuilds (-r100,-r200,... ugh). |
29 |
|
30 |
|
31 |
-- |
32 |
Ryan Hill psn: dirtyepic_sk |
33 |
gcc-porting/toolchain/wxwidgets @ gentoo.org |
34 |
|
35 |
47C3 6D62 4864 0E49 8E9E 7F92 ED38 BD49 957A 8463 |