1 |
Hi, |
2 |
|
3 |
I'm thinking of converting a few ebuilds (x11-libs/qwt, |
4 |
dev-libs/kqoauth, net-libs/qxmpp among them) to support building with |
5 |
both Qt4 and Qt5. |
6 |
|
7 |
Should this better be done by adding the corresponding useflags (qt4 |
8 |
and qt5 respectively) or by slotting? The pros and cons for each, off |
9 |
the top of my head: |
10 |
|
11 |
slotting: |
12 |
+ Allows having different use flags for qt4 and qt5 builds (can't |
13 |
think why that would be needed in the above examples though). |
14 |
- Possibility of exponential growth of the number of slots in case |
15 |
slotting would be required according to some other criteria (again, |
16 |
can't think why that would be needed in the above examples). |
17 |
- Requires keeping two different copies of the same ebuild with |
18 |
basically the same build rules, with all the consequences. |
19 |
|
20 |
useflags: |
21 |
+ Seems to be easier and doing the required trick. |
22 |
+ app-text/poppler already does this. |
23 |
- Enabling support for previously disabled Qt version requires |
24 |
rebuilding the whole library twice. |
25 |
|
26 |
What's your opinion on this? |
27 |
|
28 |
I've attached the useflag-based variant as a draft. |
29 |
|
30 |
-- |
31 |
Georg Rudoy |