Fontconfig makes sure cache files are 'up to date' by comparing the timestamp of the cache file with the timestamp of the related directory, if the cache is no older than the directory, then things are 'fine'. This works correctly when the directory and cache timestamps are under the control of the same machine. Leave the directory timestamp to another machine and things get broken if the two machines are not tightly synchronized in time. All too often, NFS has this problem. As a fix, I propose writing the directory time into the cache file and just comparing for equality. That seems far more reliable to me. This will invalidate all existing cache files though, as the cache file format will change. Anyone have concerns about this plan? -- keith.packard@xxxxxxxxx
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Fontconfig mailing list Fontconfig@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/fontconfig
