1 |
On Sat, 28 Jul 2012 14:27:49 +0800 |
2 |
Ben de Groot <yngwin@g.o> wrote: |
3 |
|
4 |
> On 28 July 2012 13:59, Nikos Chantziaras <realnc@×××××.com> wrote: |
5 |
> > On 28/07/12 08:22, Ben de Groot wrote: |
6 |
> >> |
7 |
> >> In preparation for that, we want to ask maintainers of all ebuilds |
8 |
> >> in the tree with dependencies on Qt4, to make sure that they have |
9 |
> >> the proper slot. Otherwise your package may pull in Qt5 while it |
10 |
> >> may not in fact support it. |
11 |
> > |
12 |
> > |
13 |
> > This can be trouble if the application actually works with Qt5. It |
14 |
> > might depend on Qt4 but has no problems with Qt5 (contrary to Qt3 |
15 |
> > vs Qt4, Qt5 is mostly compatible with much of existing Qt4 code), |
16 |
> > needlessly pulling-in Qt4. Many applications simply build and run |
17 |
> > as-is and no code changes are necessary. |
18 |
> > |
19 |
> > So what would be the methodology of making sure a package has the |
20 |
> > proper slot? |
21 |
> |
22 |
> Obviously you would need to make sure that the package actually does |
23 |
> support Qt5. Then, as I see it, we could do either: |
24 |
> |
25 |
> || ( x11-libs/qt-gui:4 x11-libs/qt-gui:5 ) |
26 |
|
27 |
Never prefer an old version in an || ( ) block, this makes for a poor |
28 |
update experience. Also the || ( ) construct can only be used if they |
29 |
are runtime switchable, which I really doubt here, as otherwise you |
30 |
build against one, the user install the other and portage depcleans the |
31 |
one you have built against. |
32 |
|
33 |
> |
34 |
> or: |
35 |
> |
36 |
> qt4? ( x11-libs/qt-gui:4 ) |
37 |
> qt5? ( x11-libs/qt-gui:5 ) |
38 |
> |
39 |
|
40 |
A qt5 useflag will do more harm than good. If I enable qt, I do not |
41 |
care which version, I just want the gui for the particular app. If the |
42 |
app works with qt:5 the usflag qt means qt:5, if it only works with |
43 |
qt:4 the useflags means qt:4. In case it works with both and the |
44 |
maintainer thinks it's worth to let the user choose, use the useflag qt4 |
45 |
to let the user opt out of the latest and greatest. |
46 |
|
47 |
> Other thoughts? |