After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 386521 - Create search 'backends' rather than compiling against a particular search library
Create search 'backends' rather than compiling against a particular search li...
Status: RESOLVED FIXED
Product: nautilus
Classification: Core
Component: File Search Interface
2.16.x
Other All
: Normal enhancement
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-12-16 15:38 UTC by Alex Smith
Modified: 2010-03-08 16:15 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement


Attachments
Check that tracker is actually running before using it (805 bytes, patch)
2007-09-20 16:20 UTC, Josselin Mouette
none Details | Review
Check that tracker is actually running before using it (845 bytes, patch)
2007-09-22 16:29 UTC, Josselin Mouette
committed Details | Review

Description Alex Smith 2006-12-16 15:38:25 UTC
Currently nautilus supports using a find based search backend, tracker and beagle. This is fine, but I think compiling against one backend is stupid, because as an example, I have the Frugalware Linux nautilus package compiled against tracker, but some users don't want tracker running all the time, so it's an annoyance for them. The only way they can stop using tracker without breaking search functionality would be to recompile nautilus without tracker, which a lot of people won't want to do. I think it would be much better to have the search backends compiled as nautilus extensions, and the user can select which one they want to use. That way users wouldn't be forced to use a certain search backend that they may not want.

I hope I've made that clear, if I haven't feel free to ask :)
Comment 1 Josselin Mouette 2007-09-20 16:20:20 UTC
Created attachment 95910 [details] [review]
Check that tracker is actually running before using it

There's no need for complicated architecture changes to solve this problem. This patch checks that tracker is actually installed before using it as a backend.
Comment 2 Alex Smith 2007-09-21 06:36:43 UTC
Cool, that looks good. The idea I came up with probably wasn't the best, it was just the first thing that I thought of
Comment 3 Josselin Mouette 2007-09-22 16:29:27 UTC
Created attachment 96019 [details] [review]
Check that tracker is actually running before using it

Whoops, I forgot to close the connection.
Comment 4 Sebastian Dröge (slomo) 2008-03-19 14:24:17 UTC
Ok, the tracker patch is now in trunk (will be in 2.22.1). Thanks for the patch
Comment 5 Tomas Bzatek 2010-03-08 16:15:52 UTC
I believe this issue is no longer valid, we've committed a patch that loads search engines dynamically if they're available. The only difference is that we still hardcode the order of preferred search engines: tracker, beagle, simple find. If it's still a problem for you, please open a separate bugreport.

See bug 589345 for related info.