Re: [Tracker] indexing ~/. dirs?

[Jamie McCracken <jamiemcc blueyonder co uk>]

On Tue, 2008-04-08 at 10:11 -0700, mike wrote:
> mike wrote:
> > > I haven't been able to figure out how to get
> > > directories such as ~/.dir_name into tracker to
> have
> > > tracker index what's there (I've added the paths
> in
> > > cfg file (separated/terminated correctly), didn't
> do
> > > anything; re-indexed, still didn't do anything) -
> is
> > > this possible?  I ran -v 2 and none of those dirs
> show
> > > up in the log.
> >
> > Running it with -v 3 might tell you more.
> > I have a feeling we don't search .* directories on
> purpose.
> > src/trackerd/tracker-process-files.c should tell you
> more.
> >
>
> Yes, I can see that by default it does not check any
> ~/. dirs (other than ~/.evo* and ~/.gaim) but I have
> explicitly added other ~/. to tracker cfg
> ("WatchDirectoryRoots") and it seems to be ignoring
> the additions - is that intentional too?  I realize I
> can probably just make links to them in ~/. but I
> don't want a mess of ~/ links.  
>
> Given that many ~/. may be cache dirs or others not
> suitable for searching, I can understand why the
> default is to ignore them but even when explicitly
> added to the cfg?
>
> In r0.6.6 I find no
> src/trackerd/tracker-process-files.c nor any *process*
> - is this something unreleased or just the wrong name?

it intentionally ignores hidden files and directories as we assume they
are either worthless data or belong to some other non-file service like
Conversations, emails etc

We would require some justification for allowing explicit .dir indexing

jamie