Build Fontconfig caches with active fonts - #626
Closed
jhuntwork wants to merge 1 commit into
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Font packages currently enter profiles without a matching system cache, leaving Fontconfig to rebuild metadata in mutable user or host state. Give Fontconfig a generation-owned cache and rebuild it when active packages contribute fonts, so each profile carries cache data for exactly its immutable font set while runtime caches remain available for user-installed fonts.
Keep runtime configuration under
/usr, and use a separate provider-owned realization configuration that exposes only the staged generation as a cache target. The configured release host stalls source retrieval, so use upstream's versioned GitLab snapshot for the same Fontconfig 2.16.0 source and bootstrap its build metadata.