D18664: Baloo engine: treat every non-success code as a failure

Christoph Cullmann noreply at phabricator.kde.org
Mon Feb 4 06:26:53 GMT 2019


cullmann added a comment.


  I think this is a step into the right direction.
  Thought I am still not sure if we not should go away from a own storage db for all this and port that over to e.g. use the tracker stuff.
  Given that fixing the issues will be more or less a complete rewrite, too.
  (I have some partly working port in my aged https://cgit.kde.org/clones/baloo/cullmann/tbaloo.git/)

REPOSITORY
  R293 Baloo

REVISION DETAIL
  https://phabricator.kde.org/D18664

To: valeriymalov, #baloo, bruns, poboiko
Cc: cullmann, ngraham, bruns, kde-frameworks-devel, #baloo, ashaposhnikov, michaelh, astippich, spoorun, abrahams
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20190204/f7567fa6/attachment-0001.html>


More information about the Kde-frameworks-devel mailing list