Bug#864082: [Fontconfig] Next steps for a reproducible Fontconfig?
akira at tagoh.org
Thu Jan 31 06:14:09 GMT 2019
On Thu, Jan 31, 2019 at 8:07 AM Keith Packard <keithp at keithp.com> wrote:
> We may want a command line tool that extracts data from the config
> for use by flatpak in building the dynamic configuration, including
> things like salt values per directory. Yeah, that might be made to
> work with flatpak essentially manually overriding the salt configuration
> so that it uses the flatpak-relative names.
Aha. yeah, that's a good idea.
> > This would avoid collision between one and origins. and assuming that
> > flatpaks can load config from host too, we could have:
> > 10-salt.conf (from host):
> > <salt id="default"/>
> I'd leave this out and not have salt in the host.
Sure. though implicit thing may breaks something easily like own salt
affects 'remap-dir' unexpectedly. that should be documented carefully.
or should we have salt attribute in remap-dir and dir elements
instead? that would be obvious.
> The salt here would need to have CDATA for the target directories, and I
> think flatpack wants to split the dynamic from static config bits.
> Dynamic (built at runtime):
> <remap-dir as-path="/usr/share/fonts" salt="">/run/host/fonts</remap-dir>
> Static (built in the flatpak):
> <dir salt="salt">/usr/share/fonts</dir>
Yep, that looks good to me.
> I think a dir-reset makes a lot of sense so that the flatpak can control
> the set of font paths used. Building a command-line tool that flatpak
> can use to discover the relevant fontconfig information seems like a
> useful improvement; as I recall, flatpak is currently assuming
> /usr/share/fonts and ~/.fonts are used on the host.
More information about the Pkg-freedesktop-maintainers