On Tue, 09.09.08 16:41, Colin Guthrie ([EMAIL PROTECTED]) wrote: > > Lennart Poettering wrote: > > Comments, opinions? > > Just a general one, how/when is the cache invalidated?
When the mtime of the theme root dir changes. I.e. /usr/share/theme. (See that other mail about touching that dir) > e.g. if I install a new theme etc. Is this taken care of by the current > "touching" system I noticed in the fedora spec to touch the index file > of the theme? The "touch" I had in there was bogus. It was touching the theme dir itself, not the dir the theme was stored beneath. I.e. /usr/share/theme should be touched, not /usr/share/theme/freedesktop. I now modified my spec file to touch both dirs, although there is no point in touching /u/s/t/f. I just kept it in because it might be useful later on, or maybe not. Dunno. If themes are removed they are not removed from the cache. I don't think this is much of a problem, though. The amount of data stored should not be that big. And I don't see people installing, testing and then removing millions of themes with different names. The cache is completely redundant btw. You can just delete it and it will be recreated from scratch on-demand. The cache file is stored in ~/.cache (the XDG cache dir). It has the build host string (to avoid packing/endianess issues) and a machine id in the name (because this is per-machine data on NFS $HOME). The machine id is the D-Bus UUID (if exists) or otherwise the host name. Lennart -- Lennart Poettering Red Hat, Inc. lennart [at] poettering [dot] net ICQ# 11060553 http://0pointer.net/lennart/ GnuPG 0x1A015CC4 _______________________________________________ libcanberra-discuss mailing list [email protected] https://tango.0pointer.de/mailman/listinfo/libcanberra-discuss
