| 1 |
Alan McKinnon ha scritto: |
| 2 |
> On Wednesday 08 October 2008 19:40:25 b.n. wrote: |
| 3 |
>> Erik Hahn ha scritto: |
| 4 |
>>> On Tue, Oct 07, 2008 at 11:13:33PM +0400, Andrew Gaydenko wrote: |
| 5 |
>>>> I have found another KDE app which is important sufficiently to delay |
| 6 |
>>>> switching to KDE4 - the app is k3b, which still isn't ported. If I |
| 7 |
>>>> understand well, there isn't any minimal apps list (and k3b, would be in |
| 8 |
>>>> the list, I think) which must be ported to KDE4 before unmasking KDE4 in |
| 9 |
>>>> portage. Is it so? |
| 10 |
>>> Why should there be one? The fact k3b isn't ported yet doesn't break any |
| 11 |
>>> other KDE package. |
| 12 |
>> Does k3b 3.5 run happily under kde4? |
| 13 |
>> If yes, there is no problem. |
| 14 |
>> If not, there is. |
| 15 |
> |
| 16 |
> That question is irrelevant. It should be: |
| 17 |
> |
| 18 |
> If k3b is ported to KDE4, then it will use the kde4 libs |
| 19 |
> If not, the ebuild will emerge the kde3 libs and k3b will use those. |
| 20 |
> |
| 21 |
> Either way, there is no problem. |
| 22 |
|
| 23 |
I know that *in theory* it is so. In practice however, someone in this |
| 24 |
thread has said that for example kopete suffers incompatibilities. Maybe |
| 25 |
I have not understood correctly ; however that's why I asked. |
| 26 |
|
| 27 |
m. |
Archives