On Tuesday, 2014-04-22, 17:19:37, Michael Jansen wrote: > > > I mount devices and network storage INTO my home directory. Sometimes by > > > putting the mount point into my home directory, sometimes by symlinking > > > it > > > into my home directory. I create a LOT of directories directly in my > > > home > > > directory I DO NOT WANT TO BE INDEXED AT ALL. And don't insult me by > > > telling me to blacklist each and every directory i create there manually > > > or change my workflow. If i don't get a whitelist this stuff is useless > > > for me. Why? > > > > My assumption would be that it behaves like rsync does, i.e. stays on the > > some file system. > > > > I have a similar setup, i.e. different volumes symlinked into subdirs of > > $HOME for access convenience, and rsync does not attempt to copy those > > when > > I use it for backup. > > > > Since Baloo or its KCM seems to already do mount point and device > > detection > > I would assume that it resolves mounts/symlinks before it checks its > > config. > > To much assume here. Not enough i know. That is my problem. That is why i > need a whitelist. Then its i know.
Of course. I was just pointing out that following a symlink without checking the "other" path against the lists would be a serious implementation flaw. E.g. if one adds /mnt to the blacklist, then no amount of symlinking should get anything under /mnt indexed. And it needs to do that independent of whether it uses black or white listing. Cheers, Kevin -- Kevin Krammer, KDE developer, xdg-utils developer KDE user support, developer mentoring
signature.asc
Description: This is a digitally signed message part.
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
