|
From: | Yuri |
Subject: | Re: lilypond-2.18.2 touches fontconfig database during build |
Date: | Thu, 17 Aug 2017 10:18:42 -0700 |
User-agent: | Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 |
On 08/17/17 09:54, David Kastrup wrote:
Ok, but LilyPond also accesses the system fonts when building its documentation.
Application aren't supposed to update the font cache. Package Installation procedure is supposed to do this.
Even reading installed fonts list is meaningless, because the package builder has no fonts installed, and such list is meaningless.
The right solution is to either have this as an explicit configuration option: --disable-update-system-fonts,
or to remove fontconfig altogether.I understand that you keep in mind people who will just install manually and not update fonts. But it is mostly built by package infrastructure. So maybe --disable-update-system-fonts approach is appropriate.
Yuri
[Prev in Thread] | Current Thread | [Next in Thread] |