https://bugs.kde.org/show_bug.cgi?id=427455
Nate Graham <n...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |n...@kde.org
Resolution|--- |INTENTIONAL
Status|REPORTED |RESOLVED
--- Comment #4 from Nate Graham <n...@kde.org> ---
In general, it's best to use bug reports to describe a problem rather than
proposing a solution, because there's the danger (from your perspective) that
the solution is rejected and you're left frustrated because you still have the
same problem. :)
---
And we have to reject your proposed solution, sorry. :)
Basically you are proposing using a whitelist instead of a blacklist (which is
the current approach). GNOME's Tracker uses a whitelist and behaves as you're
describing, as a point of comparison.
The problem with using a whitelist is that it puts the burden on the user to
include all of the files they care about being indexed which may be outside of
the standard XDG dirs. For example, if the user creates a folder in ~ called
"Books" and puts their books and epubs etc. in it, those files won't be indexed
under your proposal, and the user will need to know that they have to manually
include this location. That's not very user friendly. In my experience, a lot
of regular users totally ignore the ~/Documents folder and make up their own
file organization structure. Sometimes they put their thing son the Desktop,
which is an XDG location, so their files would be indexed. Sometimes they make
new folders inside ~, which results in them not being inside XDG locations, so
they don't get indexed.
---
FWIW Baloo currently has virtual disk related stuff and git repos in its
blacklist, so your examples aren't actually problems right now (unless there's
a bug). Using kdesrc-build is a corner case since by default it does
out-of-source builds (good) which results in files being created outside of the
git repos, which means they will be indexed.
For this situation, we have a few options:
1. Improve our developer documentation to specifically recommend adding ~/kde
to the "don't index these paths" list in the Search KCM
2. Have kdesrc-build do the above automatically the first time it's run
If you personally want to use the whitelist approach exclusively, you can add
your home folder to the exclusions list and then add ~/Documents to the
inclusions list.
--
You are receiving this mail because:
You are watching all bug changes.
