| 1 |
Apparently, though unproven, at 09:00 on Tuesday 01 February 2011, Mick did |
| 2 |
opine thusly: |
| 3 |
|
| 4 |
> On Monday 31 January 2011 23:31:23 Alan McKinnon wrote: |
| 5 |
> > So it's not even a learning opportunity. But upgrading to KDE-4.6.0 from |
| 6 |
> > 4.5.x when I had kbluetooth installed - now *that* was an excellent |
| 7 |
> > learning opportunity. |
| 8 |
> |
| 9 |
> Tell us more ... what are the gotchas? |
| 10 |
|
| 11 |
|
| 12 |
Portage can deal with a pure kde-4.5.x to 4.6.0 upgrade, the blockers are all |
| 13 |
soft ones so they just get automagically dealt with. |
| 14 |
|
| 15 |
But kbluetooth has this gem: |
| 16 |
|
| 17 |
COMMON_DEPEND=" |
| 18 |
<kde-base/kdelibs-4.6[semantic-desktop?] |
| 19 |
<kde-base/libkworkspace-4.6 |
| 20 |
<kde-base/solid-4.6[bluetooth] |
| 21 |
" |
| 22 |
|
| 23 |
Oops. Blocks kdelibs. Basically nothing can proceed but portage doesn't know |
| 24 |
that so it dumps about 300 lines of errors on-screen. And the poor user has to |
| 25 |
sift through all of that to find the root cause. It's there, just hidden right |
| 26 |
in the middle of all the other junk on screen |
| 27 |
|
| 28 |
|
| 29 |
-- |
| 30 |
alan dot mckinnon at gmail dot com |
Archives