Re: New module proposal: tracker

[Alexander Larsson <alexl redhat com>]

On Fri, 2009-11-06 at 18:25 +0000, Bastien Nocera wrote:
> On Fri, 2009-11-06 at 19:11 +0100, Philip Van Hoof wrote:
> > On Fri, 2009-11-06 at 17:57 +0000, Bastien Nocera wrote:
> > > On Fri, 2009-11-06 at 18:53 +0100, Philip Van Hoof wrote:
> > > > On Fri, 2009-11-06 at 09:28 -0600, Shaun McCance wrote:
> > > > > > 
> > > > > > Surely apps should ship pre-indexed help files? Or at least do the
> > > > > > indexing at install time when installing from tarballs.
> > > > > 
> > > > > All right.  Is there a suitable open format for that?  
> > > > 
> > > > Yes, the format for pre-installed content is Turtle. You have a command-
> > > > line tool and a DBus API to instruct tracker-store to import such a
> > > > Turtle file.
> > > > 
> > > > You can for example in the postinst of a package do this.
> > > 
> > > There's a tracker-store listening system-wide?
> > 
> > Hmm, that's a good point. 
> > 
> > I guess you'll have to iterate over all users and foreach
> > 
> >  su $user -c tracker-sparql -q -u $qry
> > 
> > I understand that this is not nice :(. But indeed, tracker-store isn't
> > system-wide, instead it's per user.
> 
> That won't work because you won't have access to the session D-Bus, and
> certainly wouldn't work with, say, 1k users with NFS home dirs.

Not to mention LDAP/NIS or things like that.

Its not what you want to do anyway. You want to ship the package with a
set of indexes for its help, and then when doing the query for help you
want to say "search for this string in these given installed index
files".