Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
F
fontconfig
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 152
    • Issues 152
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 17
    • Merge Requests 17
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • fontconfig
  • fontconfig
  • Issues
  • #126

Closed
Open
Opened Oct 15, 2018 by Nicolas Mailhot@nimContributor

Add a way to tell fc-query to read fontconfig files outside its default tree

The fonts autodep generator in rpm, that was written by Behdad, basically just calls

$fcquery --format '%{=pkgkit}' "${fn}" (it's in /usr/lib/rpm/fontconfig.prov)

So at it is written, it will compute query output based on the fontconfig configuration of the host system, ignoring the fontconfig files which are being installed with the font files in the build root.

It would be trivial for rpm to tell fc-query where those files are (that's just passing the /etc/fonts location in the buildroot). However, there is no flag in fc-query to receive this info

Please add such a flag

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: fontconfig/fontconfig#126