https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #37 from Joachim Wagner <jwag...@computing.dcu.ie> --- (In reply to tagwerk19 from comment #35) > Accepted. > Although I think we need to look at "what we can trust most". > [...] > This would mean including the filesystem ID in your "I" table and careful > making judgements when a disc is seen to move, vanish or reappear. Yes, a hybrid approach would be a good default as long as the filesystem ID does not change with the major:minor of the block device. For filesystems for which baloo does not know how to get a filesystem ID the ID could be "N/A" and any transition between N/A and a proper ID would also mean that the filesystem is new. > Having kept tabs on baloo issues for a couple of years, the majority of the > "reindexing" or "duplicated results" issues have been from OpenSUSE [...] The openSUSE installer uses btrfs by default. > [...] I don't remember seeing any reports mentioning > XFS [...] I don't know the status with ZFS. I'd think XFS users typically either have a simple setup or use LVM on top of a complex storage setup and LVM seems to allocate the /dev/dm-* devices in a predictable order; at least I was using this setup for many years without baloo reindexing repeatedly. > think how to deal with symbolic links 8-] This should go into a separate feature or documentation request. I see 4 decision to make, either hard-coded or configurable: (1) Symlinks to other folders: If the target folder is indexed anyway the link can be ignored. If not, the default probably should be not to follow the link as the target folder is under a folder that the user specifically excluded from indexing. (follow yes/no) (2) Indexing of the path of the target: One could index symlinks treating them like text files that contain just the target path as plain text. (index path yes/no) (3) Content indexing for symlinks to files: If the target is indexed anyway question is whether to enter the symlink as a duplicate result under a different name. If not, like for folders, the default probably should be not to index the file but this probably should be configurable as users may want to use symlinks to bring otherwise excluded files into the index. -- You are receiving this mail because: You are watching all bug changes.
