1 |
Nikos Chantziaras wrote: |
2 |
> Dmitry Makovey wrote: |
3 |
>> Hi, |
4 |
>> |
5 |
>> I was tracking KDE-4.x for a while now while sticking to "stable" |
6 |
>> KDE-3.5, which in gentoo's case is 3.5.9. Trying to get KDE-4.2 |
7 |
>> installed spits out a blocker: |
8 |
>> |
9 |
>> [blocks B ] <=kde-base/kdebase-startkde-3.5.10 |
10 |
>> ("<=kde-base/kdebase-startkde-3.5.10" is blocking |
11 |
>> kde-base/kdelibs-4.2.0) |
12 |
>> |
13 |
>> which for me means switching to *2* testing platforms (3.5.10 and |
14 |
>> 4.2) when I want to test only 1 (4.2). |
15 |
>> |
16 |
>> Now my question is: how safe is it to do a workaround, and create |
17 |
>> local version of kde-base/kdelibs-4.2.0-r1 ebuild (say, -r2) which |
18 |
>> removes the block and just stick with 3.5.9 on 3.5 side ? I really |
19 |
>> don't feel like unmasking 3.5.10 builds and building them too. |
20 |
>> |
21 |
>> another confusing thing is: |
22 |
>> !<=kde-base/kdebase-3.5.9-r4 |
23 |
>> !<=kde-base/kdebase-startkde-3.5.10 |
24 |
>> which I read as "you're fine using kde-3.5.9 as long as you don't use |
25 |
>> startkde". kind of weird. |
26 |
> |
27 |
> I know you didn't ask for this answer, but KDE 3.5.10 is *not* masked. |
28 |
> It's in ~arch. It should be a safe/stable update since it's a bug-fix |
29 |
> release (and I assume it's the last release of the KDE3 series.) |
30 |
> |
31 |
> |
32 |
> |
33 |
|
34 |
KDE-3.5.10 has been on here a while and is stable for me at least. I |
35 |
haven't checked its current status since I have not synced in a while |
36 |
anyway. |
37 |
|
38 |
OP, if you have a fairly fast machine, maybe there is some package that |
39 |
just needs to be recompiled but is getting missed for some reason. I |
40 |
would try a emerge -e world and see what that does for it. If you still |
41 |
have the same problem, may need some Raid. If not, well, it works. :-D |
42 |
|
43 |
Dale |
44 |
|
45 |
:-) |