https://bugs.kde.org/show_bug.cgi?id=473389
--- Comment #6 from tagwer...@innerjoin.org --- (In reply to Henning from comment #5) > ... doesn't baloo work reliably with links? ... The answer is somewhere between "probably not" and "I'm not sure in this case"... Baloo is built on the assumption that it can set up a one-to-one link between the filename and an internal "DocId", where the DocId is in part derived from the inode. It wants to be able to go from the filename to the DocId, then back again and get the same filename. Symlinks can mess with this assumption Baloo can work if given a symlinked folder to index but it should not meet the files via "another route" - so it should not index the files under their canonical names (or when following another symlink!). "Can work" may be a bit optimistic, it worked for me but I got a firm "don't do that" when I previously suggested this as an option. You can see that it stumbles in the trivial case here, when told to exclude $HOME and include $HOME/Documents (etc), these are Fedora defaults. Maybe this is something that can be patched, however there's an expectation that symlinks can hide "real filenames", they are not really the right tool for that... (Note that Baloo also does not "follow" symlinks when it is indexing, so if you have a separate mount and a symlink to it from your $HOME, Baloo won't index it. This is more a surprise and annoyance question rather than a reliability one though) -- You are receiving this mail because: You are watching all bug changes.
