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

Alexander Larsson alexander.larsson at gmail.com
Tue Nov 20 07:35:56 UTC 2018

On Wed, Nov 14, 2018 at 10:28 AM Akira TAGOH <akira at tagoh.org> wrote:

> Making .uuid optional would be easier. and if you can create a symlink
> from existing cache to the corresponding name with your own .uuid, we
> don't need to have mappings even. that eventually works as what
> currently fontconfig does. or do you want to use this optional uuid
> for runtime, app and user only, and mappings for host?

I was thinking of using the uuid for all the font dirs in the
runtime/app so that they never accidentally get confused with the
similarly named directories on the host.

If uuids are optional, there is no guarantees they will be set in the
host /usr/share/fonts though, so flatpak can't rely on it for those
and we need some kind of remapping configuration there.

So, one thing that is a bit suboptimal in the current uuid handling is
that each subdirectory has to have a .uuid. It would be nicer if just
we could have /usr/share/fonts/.uuid, and the subdirectories of that
could use that .uuid + md5(relative-path) as the key. Then what we're
talking about is a single file rather than files all over the place.

More information about the Fontconfig mailing list