[Fontconfig] [PATCH] Do not remove UUID file when a scanned directory is empty
keithp at keithp.com
Mon Oct 29 22:05:00 UTC 2018
Akira TAGOH <akira at tagoh.org> writes:
> That wouldn't be impossible though that needs to change the logic a
> lot. but yes, that would be sane way and better doing like what
> fontconfig deals with caches, in the future.
Hrm. I didn't understand what the uuid files were being used for.
Reading through the code, it looks like they are an attempt to share
cache files when there is more than one path name used for the same
directory? And that by storing the UUID file in the font directory, you
provide a stable name for the cache file even if the directory is
accessed through a different path name.
If this is true, then I'm not sure I can see how we could move the .uuid
files to a separate directory and retain this property.
Is my understanding of why this mechanism was created correct? If so,
I'd like to suggest that we just remove it; I think it's more important
for fontconfig to avoid modifying the font directories than for it to
avoid replicating cache information in the (rare?) case that there is
more the one path to the same font directory.
We could use the 'realpath(3)' function during the generation of the
cache file name; that would at least avoid having symlinks cause
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 832 bytes
Desc: not available
More information about the Fontconfig