block: plasma needs baloo:5, dolphin:4 can't

[ExecutorElassus]

Happy New Year, to those of you that use that calendar.

I'm trying to remerge packages to deal with gcc's new ABI (following the gentoo news item that points to this blog).

However, as part of the rebuild, I'm running into a dumb set of package blocks, which I hope you folks can help me resolve:

[Perfect Gentleman]

[asturm]

@Perfect Gentleman: That's no solution, packages are present that will pull both baloos back in.

Don't you use the plasma profile? OK FVWM, obviously not.

[ExecutorElassus]

Some other app (I can't remember now, but recent) in the KDE ecosystem requires baloo with '-minimal', which was the start of this whole problem.

So, in short: dolphin:5 sucks horribly outside of kde, but I apparently can no longer use dolphin:4 because it depends on baloo:4, which plasma-workspace and plasma-desktop no longer accept.

Somewhat off-topic: is this a trend in the two main WMs that still isn't being reconsidered? I mean, it seems both the KDE and GNOME devs are pushing a unified UI model, such that their apps no longer work in isolation, and depend on a monolithic installation to work. I almost got into a flamewar with a dev from the Unity project, because their WM now explicitly ignores .xmodmap and provides no alternative, on the grounds that letting users set their own keybindings "makes it impossible to present a coherent UI" (ie, it's not a bug, it's a feature). My solution to that was to ditch Unity altogether in favor of enlightenment. But now KDE is how many years into version 5, and one of their main apps -- a file manager, of all things -- still cannot function without being within its own WM, and they are pushing users into that WM more insistently (by, for example, this requirement of baloo with -minimal, which seemingly forces baloo:5). I thought the linux way rested on modularity, simplicity, robustness, and ease of customization (among other things), and the apparent insistence on a single WM ecosystem goes against that. Grrrr! /rant

Thanks for the help. Krusader seems like a nice file manager (though a two-pane file manager doesn't fulfill any but rare use cases for me).

EE

[asturm]

[iandoug]

hi

I use USE=minimal to get emerge to function, is there a better way around this?

[asturm]

That's exactly the way it is planned.

Using plasma profile solves this automatically for you.

[iandoug]

[asturm]

You're not using Plasma-5, but installing kf5-based applications? Imo amd64 users should use KDE4 (and stay away from kf5 upgrades), ~amd64 users should migrate to Plasma-5 as they will get more and more applications upgrades that do not really work well within Plasma-4.

No, PIM hasn't made it to tree yet. It remains in kde overlay until it is deemed fit for addition to tree.

[iandoug]

[asturm]

Well, USE=minimal (in package.use - NOT globally!) IS the solution, or do you still see a block?

[msst]