[Fontconfig] [PATCH] Do not remove UUID file when a scanned directory is empty

Akira TAGOH akira at tagoh.org
Mon Oct 29 12:19:20 UTC 2018

On Sat, Oct 27, 2018 at 4:35 AM Keith Packard <keithp at keithp.com> wrote:
> Could these UUID files be placed in the cache directory instead of the
> font directories? That would avoid the directory mtime problem
> entirely.

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.

> > Resetting the mod timestamp of the directory seems not help for
> > AppArmor issue at least. they don't want to see the file
> > creatioin/removal at the runtime.
> That makes sense -- random applications should not be writing to font
> directories. If the UUID files need to live in the font directories,
> they should only be created by fc-cache.
> I would argue that they should not be removed for empty directories; the
> presence of the UUID file should be the signal that fc-cache has scanned
> a directory; removing it for empty directories makes this signal
> ambiguous.
> --
> -keith


More information about the Fontconfig mailing list