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

"Keith Packard" <[email protected]> Fri, 26 Oct 2018 12:35:48 -0700

Newsgroups	gmane.comp.fonts.fontconfig
Message-ID	<[email protected]>

Akira TAGOH <[email protected]> writes:

> Removed from where? fontconfig still has it at least though.

When a directory has no subdirectories or font files, we get:

        Create UUID file (preserving mtime)
        scan directory
        Remove UUID (updating mtime)

This happens every time anyone scans the directory, so the mtime is
changed at each scan.

Could these UUID files be placed in the cache directory instead of the
font directories? That would avoid the directory mtime problem
entirely.

> 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

_______________________________________________
Fontconfig mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/fontconfig

signature.asc (application/pgp-signature, 832 B)