Re: [Tracker] Tracker daemon/indexer responsibilities

[Jamie McCracken <jamie mccrack googlemail com>]

On Thu, 2008-06-26 at 17:26 +0200, Carlos Garnacho wrote:
> Hi!,
>
> On jue, 2008-06-26 at 09:47 -0400, Jamie McCracken wrote:
>
> <snip>
>
> > the desktop/ini file will contain fields for :
> >
> > directories to watch
> > recursive directories to watch
> > ignore directories regex
> > files to index regex
> > files to ignore regex
> > index executable
> > index module name
> > file mime types
> > service name
>
> ïI've been thinking a while about how to be able to get tracker-indexer
> modules to be build of of the tracker tree (so they can be provided by
> separate app, and tracker would just make use of them).
>
> Basically, besides having to install a few headers and turn a couple of
> basic things into a installable library, modules should be able to
> define custom services and metadata types. And also there's the problem
> that a single module wants to provide data for several services.
>
> So, IMHO tracker should be able to read all files from (say)
> $prefix/share/tracker/services/ to create the ontology, instead of just
> reading a few hardcoded files as it's right now.

yes absolutely - we need to remove all hardcoding but that can wait til
re-architecture is finished. 

I think its important we get to the stage where refactor and
re-architecture is complete before adding more features otherwise it may
be never-ending

> This, plus a way from modules to specify the service to use when storing
> certain metadata would make things quite flexible, resorting to get the
> service for the given mimetype if none was provided.
yes makes sense


jamie