| 1 |
On Fri, Jul 27, 2012 at 11:56 PM, Nikos Chantziaras <realnc@×××××.com> wrote: |
| 2 |
> On 28/07/12 09:46, Davide Pesavento wrote: |
| 3 |
>> |
| 4 |
>> On Fri, Jul 27, 2012 at 11:27 PM, Ben de Groot <yngwin@g.o> wrote: |
| 5 |
>>> |
| 6 |
>>> On 28 July 2012 13:59, Nikos Chantziaras <realnc@×××××.com> wrote: |
| 7 |
>>>> |
| 8 |
>>>> [...] |
| 9 |
>>>> |
| 10 |
>>>> So what would be the methodology of making sure a package has the proper |
| 11 |
>>>> slot? |
| 12 |
>>> |
| 13 |
>>> |
| 14 |
>>> Obviously you would need to make sure that the package actually does |
| 15 |
>>> support Qt5. Then, as I see it, we could do either: |
| 16 |
>>> |
| 17 |
>>> || ( x11-libs/qt-gui:4 x11-libs/qt-gui:5 ) |
| 18 |
>>> |
| 19 |
>> |
| 20 |
>> This is wrong because qt4 and qt5 are not binary compatible. |
| 21 |
>> |
| 22 |
>>> or: |
| 23 |
>>> |
| 24 |
>>> qt4? ( x11-libs/qt-gui:4 ) |
| 25 |
>>> qt5? ( x11-libs/qt-gui:5 ) |
| 26 |
>>> |
| 27 |
>> |
| 28 |
>> This is the only alternative AFAICS. |
| 29 |
> |
| 30 |
> |
| 31 |
> In that case, if Qt5 is installed, the application might depend on Qt4, but |
| 32 |
> when building it, might link against Qt5. |
| 33 |
> |
| 34 |
> |
| 35 |
|
| 36 |
No, that would be a bug in the ebuild or somewhere else. |
| 37 |
|
| 38 |
BTW, I'm planning to write a qt5-utils.eclass, which will provide an |
| 39 |
eqmake5 function similar to eqmake4 in qt4-r2.eclass. |
| 40 |
|
| 41 |
Cheers, |
| 42 |
Pesa |
Archives