On Thu, Apr 4, 2019 at 1:09 PM Akira TAGOH <akira@xxxxxxxxx> wrote: > > On Thu, Apr 4, 2019 at 5:46 PM Alexander Larsson > <alexander.larsson@xxxxxxxxx> wrote: > > There are still some issues though: > > * Only flatpak 1.2.0 and later generates the dir-remapping fontconfig > > file, so earlier versions of flatpak will regenerate caches for > > /run/host/fonts. > > * On current distros, with the uuid file generated the host fc-cache > > will only generate the uuid style cache files, and these will not be > > used by the fontconfig in the sandbox. > > > > The first I think is fine, just update your flatpak to the latest > > stable release and it will be fast. > > > > However, the second is a problem. It means that the second we update > > the flatpak runtime to the latest fontconfig all flatpak apps will get > > a slow first startup on all current distros. > > > > Is it possible that we could make the new fontconfig not generate uuid > > cache files, but look for them as fallback? I.e. if the (possibly > > salted) regular path checksum doesn't exist, look for a .uuid file in > > that dir and use that for lookup? > > Yes. done. hope that works well. Yes, this now seems to work well. I think this is good to go! _______________________________________________ Fontconfig mailing list Fontconfig@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/fontconfig
