Bug 180460

Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

I have some music and photos on an external harddisk. Since KDE4 does not yet support automounting, the external harddisk is not available when KDE4 starts up. If I check which folder strigi/nepomuk is working on, I see that they work on the external harddisk, which cannot be true, since it is not available. So I guess it is removing data, which it obviously has to re-add later on.

If this is true, this means that a lot of CPU is wasted when removing and re-addign data. It would be nice if there was some smarter way to handle this kind of situation, either automatically, or by allowing the user to give nepomuk/strigi a hint on which folders are removeable and which are not.

For example, if the external harddisk is mounted in /media/external and the user selected /media/external (which includes the sub-tree) to be indexed, strigi/nepomuk should do nothing, i.e. not remove any data, if that folder, i.e. the "root folder of /media/external", is not available. It should not show results from it either.

If however /media/external/music, i.e. a sub-folder of /media/external) does not exist anymore, but /media/external does, it can update its index and remove the data about /media/external/music.

The only way strigi/nepomuk would remove data for /media/external while /media/external not being available would be, if the user de-selects that folder in the index settings.