I’m happy to see that distributors are starting to package Tracker 3, and there’s an interesting discussion which began at here about why we made Tracker 3 parallel installable with Tracker 2.
As we mentioned in our GUADEC 2020 talk, it’s a complex task to coordinate the changes in Tracker with the various places Tracker is used in GNOME. We didn’t know if it’d be possible to port everything in a single cycle. In fact, we still don’t know! I put out a call for testing which may lead to us discovering some critical issue. Our initiative to port all apps to Tracker 3 is still in progress too – some of the tasks depend on volunteer maintainers having time to review changes.
The good thing about making Tracker 3 parallel installable with Tracker 2 is that we have options. Our “Plan B” for the GNOME 3.38 release, if it’s not possible for every app to update to Tracker 3 in time, is that GNOME 3.38 would depend on Tracker 2 for full-text search and the apps which aren’t ported, but we would release a “off-by-default” Tracker 3.0 that the apps which are ported can use to index e.g. the
@kloczek made the point that it’s difficult to have a ‘tracker’ package that upgrades cleanly from tracker 2.x to tracker 3.x if the systemd services change names. I don’t have a good answer for that. I am wondering if – given that we may yet have to do the “Plan b” described above – we should ask distributors to create a new tracker3 package in all cases.