On Monday, 2014-04-21, 16:53:16, Michael Jansen wrote: > > This has been discussed in detail at > > http://lists.kde.org/?l=kde-devel&m=139606131629659&w=2 . tl;dr - There > > won't be an option to disable Baloo or an include list. Baloo might > > however > > show list of currently indexed dirs. > > I really hope they reconsider. > > I was always a fan of nepomuk. Used it all the time. Improved it with small > patches and quite some patches for crashes. Worked with them on performance > issues. This is the first time i consider disabling it completely myself. > > Because it seems its going in a direction that completely breaks my style of > work. And puts me into potential legal troubles. > > 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. 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 <<
