Bug 386775

Summary:	Additional whitelist option to configure Baloo in the systemsettings
Product:	[Applications] systemsettings	Reporter:	PK <pieterkristensen>
Component:	kcm_baloo	Assignee:	Pinak Ahuja <pinak.ahuja>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description PK 2017-11-12 15:00:10 UTC

My problem: 
How do you get baloo to index a folder on an external partition?

- Add the whole partition? That could turn out to be very expensive if the partition is big, 
- blacklist all other folders on that partition? That could be really not practical if there are a lot of folders on the partition.

Comment 1 PK 2017-11-12 15:27:29 UTC

I come to think of it: I suppose there are circumstances wherein it should be far more practical to have an additional whitelist option when the folder you want to index is on the / partition too.

Comment 2 Christoph Feck 2017-11-24 00:26:37 UTC


*** This bug has been marked as a duplicate of bug 352487 ***

Comment 3 PK 2017-11-24 04:10:52 UTC

In my opinion this is not a duplicate of bug 352487. In that bug the question is to replace the blacklist system by a whitelist system. I can see that only whitelisting can bring problems too.
That is why I suggest to have AND the possibility to blacklist AND the possibility to whitelist.

Comment 4 Christoph Feck 2017-12-20 18:07:37 UTC

The comments in bug 352487 make it clear that both lists are needed.