Make KF5Baloo optional
Review Request #128956 - Created Sept. 20, 2016 and submitted
Regardless of the current state of Baloo, it is not very deeply tied into Plasma. Usage in plasma-workspace comes down to providing the baloo runner.
Several days of Plasma-5 without any issues. Usage of krunner without any segfaults.
Why not add logic to the runner to disable it automatically in the appropriate conditions? It doesn't have to be as simplistic as "there is no Baloo database at all". The other Andreas sort of suggested that and dismissed it right away but I think it's a good idea.
For example, it could be tri-state: Disabled by default if Baloo file search is disabled, enabled if file search is enabled, or explicitly enabled / disabled. While it's ugly, it also covers the case that somebody uses only E-mail indexing. E-mail indexing is super useful IME, and somebody might want to use it from krunner. I just use it from KMail, though...
One could also add an option to the Baloo KCM to clear the file index, which would automatically disable the runner (not sure if this is doable with a small amount of work / code).
I don't think it is a good idea to effectively make distributions choose Baloo support or not in krunner. If they still really want to, they can probably use the cascading feature of KConfig and supply a global config file that disables the Baloo runner by default.