| 1 |
Sergey Popov wrote: |
| 2 |
> qt? ( |
| 3 |
> qt5? ( dev-lang/qtcore:5 ) |
| 4 |
> !qt5? ( dev-lang/qtcore:4 ) |
| 5 |
> ) |
| 6 |
> |
| 7 |
> Fine by me, if you would ask. |
| 8 |
|
| 9 |
May I suggest instead: |
| 10 |
|
| 11 |
qt? ( |
| 12 |
qt5? ( dev-lang/qt$something:5 ) |
| 13 |
qt4? ( dev-lang/qt$something:4 ) |
| 14 |
) |
| 15 |
|
| 16 |
|
| 17 |
Alexandre Rostovtsev wrote: |
| 18 |
> > qt? ( |
| 19 |
> > > qt5? ( dev-lang/qtcore:5 ) |
| 20 |
> > > !qt5? ( dev-lang/qtcore:4 ) |
| 21 |
> > ) |
| 22 |
> > |
| 23 |
> > Fine by me, if you would ask. |
| 24 |
> |
| 25 |
> That flag should be called "gui". Not "qt". |
| 26 |
> |
| 27 |
> This would be the real solution to gnome team's gtk/gtk2/gtk3 flag |
| 28 |
> problem and to qt team's flag problem too. |
| 29 |
|
| 30 |
Unlike gtk+, using Qt does not mean that there is any GUI. |
| 31 |
|
| 32 |
Qt provides many things, and sometimes non-GUI Qt bits are used |
| 33 |
independently in console-only applications. |
| 34 |
|
| 35 |
|
| 36 |
//Peter |
Archives