| 1 |
On Wednesday 08 October 2008 19:40:25 b.n. wrote: |
| 2 |
> Erik Hahn ha scritto: |
| 3 |
> > On Tue, Oct 07, 2008 at 11:13:33PM +0400, Andrew Gaydenko wrote: |
| 4 |
> >> I have found another KDE app which is important sufficiently to delay |
| 5 |
> >> switching to KDE4 - the app is k3b, which still isn't ported. If I |
| 6 |
> >> understand well, there isn't any minimal apps list (and k3b, would be in |
| 7 |
> >> the list, I think) which must be ported to KDE4 before unmasking KDE4 in |
| 8 |
> >> portage. Is it so? |
| 9 |
> > |
| 10 |
> > Why should there be one? The fact k3b isn't ported yet doesn't break any |
| 11 |
> > other KDE package. |
| 12 |
> |
| 13 |
> Does k3b 3.5 run happily under kde4? |
| 14 |
> If yes, there is no problem. |
| 15 |
> If not, there is. |
| 16 |
|
| 17 |
That question is irrelevant. It should be: |
| 18 |
|
| 19 |
If k3b is ported to KDE4, then it will use the kde4 libs |
| 20 |
If not, the ebuild will emerge the kde3 libs and k3b will use those. |
| 21 |
|
| 22 |
Either way, there is no problem. |
| 23 |
|
| 24 |
Besides, isn't k3b NOT part of the official KDE tarballs (like amarok)? If so |
| 25 |
it can't hold up KDE4. |
| 26 |
|
| 27 |
|
| 28 |
|
| 29 |
-- |
| 30 |
alan dot mckinnon at gmail dot com |
Archives