| 1 |
Dmitry Makovey wrote: |
| 2 |
> Hi, |
| 3 |
> |
| 4 |
> I was tracking KDE-4.x for a while now while sticking to "stable" KDE-3.5, which in gentoo's case is 3.5.9. Trying to get KDE-4.2 installed spits out a blocker: |
| 5 |
> |
| 6 |
> [blocks B ] <=kde-base/kdebase-startkde-3.5.10 ("<=kde-base/kdebase-startkde-3.5.10" is blocking kde-base/kdelibs-4.2.0) |
| 7 |
> |
| 8 |
> which for me means switching to *2* testing platforms (3.5.10 and 4.2) when I want to test only 1 (4.2). |
| 9 |
> |
| 10 |
> Now my question is: how safe is it to do a workaround, and create local version of kde-base/kdelibs-4.2.0-r1 ebuild (say, -r2) which removes the block and just stick with 3.5.9 on 3.5 side ? I really don't feel like unmasking 3.5.10 builds and building them too. |
| 11 |
> |
| 12 |
> another confusing thing is: |
| 13 |
> !<=kde-base/kdebase-3.5.9-r4 |
| 14 |
> !<=kde-base/kdebase-startkde-3.5.10 |
| 15 |
> which I read as "you're fine using kde-3.5.9 as long as you don't use startkde". kind of weird. |
| 16 |
|
| 17 |
I know you didn't ask for this answer, but KDE 3.5.10 is *not* masked. |
| 18 |
It's in ~arch. It should be a safe/stable update since it's a bug-fix |
| 19 |
release (and I assume it's the last release of the KDE3 series.) |
Archives