Re: Next steps for a reproducible Fontconfig?
Alexander Larsson <[email protected]> Fri, 11 Jan 2019 12:19:55 +0100
| Newsgroups | gmane.comp.fonts.fontconfig |
|---|---|
| Message-ID | <CAHr-LrbnK6nQ2+dkpaR45NKVD0amJNm_S4dQBjexcof-GZiRJA@mail.gmail.com> |
On Fri, Jan 11, 2019 at 12:17 PM Akira TAGOH <[email protected]> wrote: > > On Thu, Jan 10, 2019 at 7:54 PM Alexander Larsson > <[email protected]> wrote: > > Here is my proposal: > > > > Make the uuid *generation* optional and manual. Then, when we create > > the flatpak runtime we run fc-cache --make-uuid (or something) to > > generate the uuid files. Then fontconfig would never confuse the > > sandboxed /usr/share/fonts with any other, and since we would get a > > new uuid each time we regenerated the runtime it would correctly pick > > up stale caches when we update the runtime (even with no mtime > > change). > > This would requires the root privilege to create uuid file on > directories where root own though, are you going to have setuid to > flatpak? > or can this be done without it? This would be done when creating the runtime, and at that time we have write rights to /usr. Its not actually owned by root by that time though, we build the image as some other user. _______________________________________________ Fontconfig mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/fontconfig