Version: (using KDE 4.3.1) OS: Linux Installed from: Unlisted Binary Package I get the feeling my Nepomuk store size is only growing and growing... When deleting previously indexed files, and when adding new Strigi index exclude filters in the Nepomuk configuration, the Nepomuk store should properly shrink to exactly the same state as if .kde/share/apps/nepomuk/repository were deleted and everything re-indexed from scratch.
Deleting previously indexed files should already be handled. The size of the db, however, is no good indicator. It ca fluctuate based on internal states. It would be better to test like this: sopranocmd --model main --dbus org.kde.NepomukStorage list "<file:///home/me/path/to/a/deleted/file> Also be aware that removed files are only picked up at the next big sweep, not immedeately. Could you please test the above.
Okay, I can confirm that according to the sopranocmd command deleting previously indexed files does in fact remove the corresponding data in the index. However, so far I can't see any effect of removing an entry from the exclude filters list. (Is there any way to manually force one of those "big sweps"?)
To update all folders call: qdbus org.kde.nepomuk.services.nepomukstrigiservice /nepomukstrigiservice org.kde.nepomuk.Strigi.updateAllFolders
This is done automatically on config change now.