Bug 352487 - Please offer a whitelist instead of blacklist mode for file indexing
Summary: Please offer a whitelist instead of blacklist mode for file indexing
Status: RESOLVED FIXED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_baloo (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR wishlist
Target Milestone: ---
Assignee: Pinak Ahuja
URL:
Keywords:
: 333743 354838 386775 (view as bug list)
Depends on:
Blocks:
 
Reported: 2015-09-09 16:06 UTC by jm.ouwerkerk
Modified: 2020-08-10 13:43 UTC (History)
12 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jm.ouwerkerk 2015-09-09 16:06:25 UTC
Please consider adding a whitelist version of the blacklisting functionality in the baloo file indexer KCM.

Rationale: it's possible to have lots of stuff dumped in $HOME that you don't particularly want baloo to index such as:
 - Virtual machines, disk images, config files.
 - Locally installed applications, related settings and resources
 - Object files and other results of some compiler transforming some source file.
 
Still even in that case it would be useful to have baloo index *some* locations like ~/Documents or ~/Pictures

In such situations it is much easier and quicker to whitelist things you do want baloo to index because you necessarily know that these places exist, but you may not necessarily know what cruft is generated by 3rd party software like a vendor IDE, SDK or remote desktop apps. 

Examples that spring to mind: repackaged versions of Eclipse such as LPCExpresso, Matlab, VHDL/Verilog tooling, Android SDKs, kdesrc-build and its output, stuff downloaded with GHNS (like 3rd party wallpapers, text editor snippets, plasma widgets).

Reproducible: Always
Comment 1 Hussam Al-Tayeb 2015-09-26 13:18:11 UTC
As I mentioned in Bug 353193, the key here is to only index relevant folders (which makes searches return only relevant items) and allow the user to add additional folders.
Comment 2 Christoph Feck 2015-11-04 22:53:09 UTC
*** Bug 354838 has been marked as a duplicate of this bug. ***
Comment 3 PK 2016-03-21 18:03:50 UTC
And then there is this problem:
how to add a folder to the search and index of Baloo that is on an other partition?
In this case a white-list option would be great!
Comment 4 Koen 2016-04-26 21:18:02 UTC
I also think a whitelist should preceed a blacklist.
The current blacklist aswell as the new whitelist functionality should be editable in the kde 'file search' control module as well.

Basic functionality IMO.
Comment 5 Koen 2016-04-28 17:46:41 UTC
After looking again, the whitelist is already there, isn't it?

Basically the 
folders[$e]=/folder1,/folder2

Am I right?
Comment 6 PK 2016-04-28 17:58:06 UTC
I'm using kde Neon at the moment. I read that they made a whitelist option but on my system it is still not there. I guess I have to be a little patient.
Comment 7 Rex Dieter 2016-04-28 17:59:44 UTC
The indexing code supports whitelisting, it's just not exposed in any UI (yet)
Comment 8 Christoph Feck 2017-11-24 00:26:37 UTC
*** Bug 386775 has been marked as a duplicate of this bug. ***
Comment 9 Martin M 2019-05-08 06:46:01 UTC
The existing whitelist functionality is only for folders, as far as I can see. A related topic is also to whitelist file types. 

For example, baloo will not index text files with the extension .org (as explained here https://askubuntu.com/q/1130784/244753). It would be good if one could explicitly add file extensions to the list of files being indexed.
Comment 10 Nate Graham 2019-11-12 20:04:18 UTC
*** Bug 333743 has been marked as a duplicate of this bug. ***
Comment 11 PK 2020-08-10 06:20:28 UTC
I am using Neon KDE with plasma 5.19.4 and as far as I can see this bug is fixed. KDE became even more usable!
Great! If I am not mistaking this bug could be marked as "fixed"...
Comment 12 Nate Graham 2020-08-10 13:43:42 UTC
Indeed, this was implemented in 5.19!