Mike FABIAN
2006-Feb-10 15:13 UTC
[Fontconfig] Patch: prefer cache files in /var/cache/fontconfig over <dir>/fonts.cache-2
Takashi made a patch to prefer the cache files in /var/cache/fontconfig over cache files in the directories where the fonts are. The current behaviour is the opposite, i.e. the fonts.cache-2 files in the directories where the fonts are are preferred. We think it is better to prefer the caches in /var/cache/fontconfig because the directories where the fonts are (e.g. /usr/share/fonts) might be mounted readonly, maybe from some server via NFS. If there is a problem with these cache files in the font directories, there is Currently no way to fix the problem on a machine mounting these directories readonly. /var/cache/fontconfig should be writeable, therefore one can create good caches by calling "fc-cache -f". But this won''t help if the because the broken cache files cannot be removed from the readonly file system, the broken cache files are still preferred. Because "fc-cache -f" can always create good caches in /var/cache/fontconfig, the caches there should be preferred. -------------- next part -------------- A non-text attachment was scrubbed... Name: fc-prefer-var-cache.diff Type: text/x-patch Size: 1764 bytes Desc: not available Url : http://lists.freedesktop.org/archives/fontconfig/attachments/20060211/1baade07/fc-prefer-var-cache.bin -------------- next part -------------- -- Mike FABIAN <mfabian@suse.de> http://www.suse.de/~mfabian ?????????????
Patrick Lam
2006-Feb-10 21:03 UTC
[Fontconfig] Patch: prefer cache files in /var/cache/fontconfig over <dir>/fonts.cache-2
Mike FABIAN wrote:> We think it is better to prefer the caches in /var/cache/fontconfig > because the directories where the fonts are (e.g. /usr/share/fonts) > might be mounted readonly, maybe from some server via NFS.This sounds sensible to me. I originally made it read the fonts directory first because that was the inverse of the order in which it tries to write, but there''s no good reason to invert the order here, and /var/cache/fontconfig seems more likely to be correct, especially since it''s the first place that fc-cache tries to write to! I''ve committed the patch. pat