Re: [Tracker] Bug 509601: make tracker-extractor modular

[Luca Ferretti <elle uca libero it>]

Il giorno lun, 28/01/2008 alle 12.20 +0100, Carlos Garnacho ha scritto:
> Hi!,
>
> In bug #509601 there's a patch attached to make extractors GModules, so
> tracker-extractor loads them at startup instead of having a fixed array,

Only startup? :-(

I mean, could be really awesome load them when "installed" (and maybe
provide a per-user directory, like gstreamer plugins). Something like:

      * I found a new module to extract data from XYZ format ("Hey, I've
        some XYZ files in my home, this is useful!")
      * I copy it in $HOME/.tracker/extractors/ ("Damn! I've no
        superuser privileges")
      * Tracker Applet shows an alert like

        <b>New data extractor available</b>
        
        A new extractor for files XYZ. Tracker will
        scan your data searching for XYZ files and
        will extract info from them
        
                                             ( OK )

BTW this means that, ideally, we could disable some extractors

> This may be interesting if some application wants to provide its own
> metadata extractor.

The real issue IMHO is that we have too much dependencies. Of course
most of them are optionals, but I think split tracker in tracker-core
(depends only on glib, sqlite and dbus), tracker-extractors (depends on
tracker-core and libraries to extract metadata) and tracker-gui (depends
only on tracker-core and GTK+) will be really helpful for vendors and
thirty part developers.

>  I'd appreciate any testing :)

Applied on my jhbuild sandox and reindexing my betatester user data.

Any special test to perform?