Re: [Tracker] Enhancement proposal: Automatic reindexing when adding new extractors

[Adrien Bustany <madcat mymadcat com>]

On Wed, 17 Feb 2010 10:36:01 +0000, Martyn Russell <martyn lanedo com>
wrote:
> On 15/02/10 19:51, Adrien Bustany wrote:
> > On Mon, 15 Feb 2010 17:22:56 +0000, Martyn Russell<martyn lanedo com>
> > > Well, most applications have their own desktop file which includes a
> > > list of mime types they support. So why not use that?
> > True, but that means that we have to modify the desktop file when we
add
> > a desktop file... Which is complicated from a packaging POV. Or I
didn't
> > get your point?
>
> If you mean modify the new ini type file (we are talking about here) 
> when we modify the applications actual desktop file, then yes, we would.

> I suppose it depends on how you decide if the file has been updated 
> here. If we keep some internal md5sum of the original .desktop file then

> we don't have to change two files, but simply implement a method of 
> storing the md5s.
But do we have one desktop file per extractor here, or one for Tracker ?
The idea was to be able to update extractors independantly from Tracker
itself...
> > > > > The ShouldReindex is a simple toggle to know if we need to start a
> > > > > reindex or not. You could possibly change this to ShouldIndex=mimes
so
> > > > > you only handle particular mimes? (not sure if that makes sense
> > > > > though).
> > > > It probably makes sense for an extractor that handles several types
> > > > (eg. the gstreamer one)
> > >
> > > Several mime types? Not sure I follow your point here?
> > A single extractor can support several mime types. We only want to
> > reindex
> > the relevant ones when needed.
>
> Right, so if ShouldReindex was not a true or false value, but rather a 
> string list of mime types to reindex, we would know which mime types 
> (out of ALL mime types the actual .desktop file lists) to reindex.
That would be better I think.