BTW, Hrvoje, I can confirm your experience with repeated rebuildings
of the dir file.
>>>> "Hrvoje" == Hrvoje Niksic
<hniksic(a)iskon.hr> writes:
Hrvoje> sperber(a)informatik.uni-tuebingen.de (Michael Sperber
Hrvoje> [Mr. Preprocessor]) writes: 1) I meant: cache between two
Hrvoje> invocations of XEmacs.
> But if you want to do this, the dir files are, by design,
> *exactly* the place for such a cache.
Hrvoje> Except that the dir files are not writable for the user.
Hrvoje> Do you all people run as root or something? :-)
No. Furthermore, under Linux I don't trust the sysadmin (in practice,
Red Hat, SuSE, Debian, et al, plus a multitude of free-lance
package-releasers) to keep the dir files accurate or even consistent.
Nor do dir files have certain information (time-stamps and/or
checksums) that would be useful in keeping a true cache consistent,
and nowhere to put it.
> If you introduce another cache level, you now have 2 possible
> levels of inconsistency.
Hrvoje> Do I have a choice?
No, I don't see one. Furthermore, Michael, I don't understand you of
all people making this objection. I thought you advocated automatic
building of lists of files and things whenever possible, precisely
because you think XEmacs can get it as right as anybody does? If so,
shouldn't the only cache we trust be one we make ourselves?
And hell, if we have to make our own cache, maybe we can add an API to
allow programmers to help the user to see the things they look at most
often first? And a UI for the user to set those things themselves,
and to decide when to refresh the cache?
--
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091
/* What's the big deal about the millennium? .............................
.... There are still 360 shopping days left until the millennial epoch! */