If the database exists in the old XDG Data location, migrate it to the XDG cache location.
Details
Details
Diff Detail
Diff Detail
- Repository
- R293 Baloo
- Branch
- master-xdgCache (branched from master)
- Lint
No Linters Available - Unit
No Unit Test Coverage
Comment Actions
This is a follow up of https://git.reviewboard.kde.org/r/129605/ (and the related discussion)
Comment Actions
FWIW I'm in favor of this. XDG_CACHE_HOME seems appropriate since the data is easily regenerate-able, and we try to move the existing DB to the new location to prevent a re-index.
Comment Actions
The way I use baloo the DB is not easily recreated at all.
- Indexing takes around 2hrs.
- On top of that I have to make a lot of manual adjustments due some bugs in baloo. That takes about another hour.
In my view a cache is for faster access of data that already exist somewhere else. "non-essential" data as freedesktop Standard states. The baloo db, though recreatable, definitely is essential data and as such belongs to XDG_DATA_HOME.
Putting something into XDG_CACHE_HOME is communicating to the users. "You can delete these data without harm".
At least in my case that is not true.
IMO the db should stay at its current location.