otaylor(a)redhat.com (Owen Taylor) writes:
> ~/.fonts.cache-1 is shared between machines whose
font-directories
> might have different timestamps. When started on machine A, the
> ~/.fonts.cache-1 file can contain the timestamps of machine B and
> applications will regenerate the cache therefore. The same repeats
> on machine B because fonts.cache-1 has now the machine A
> timestamps. Now, the recursion starts at A again...
If you always run fc-cache on the parent directory (*) of any place you
install fonts, then this shouldn't be an issue.
This seems to be a bug in the %post scriptlets of the
font-packages. E.g. /usr/share/fonts/zh_TW/TrueType/ contains
| -rw-r--r-- 1 root root 8586 25. Jul 14:11 fonts.cache-1
| -rw-r--r-- 1 root root 945 28. Jul 21:26 fonts.dir
When calling the questionable /usr/bin/redhat-update-gnome-font-install*
programs manually, the timestamp of fonts.cache-1 does not change. But
since the directory is changed by rpm's cpio, the local ~/.fonts.cache-1
will be updated.
The same happens with /usr/X11R6/lib/X11/fonts/{75dpi,Type1,misc} which
are having very old fonts.cache-1 files (Jan 08, 2003).
Enrico