[Bug 194957] New: x11-fonts/linux-{c6,f10}-fontconfig: linux- apps pollute user cache with system fonts on amd64

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194957

            Bug ID: 194957
           Summary: x11-fonts/linux-{c6,f10}-fontconfig: linux- apps
                    pollute user cache with system fonts on amd64
           Product: Ports Tree
           Version: Latest
          Hardware: Any
                OS: Any
            Status: Needs Triage
          Severity: Affects Only Me
          Priority: ---
         Component: Infrastructure
          Assignee: emulation at FreeBSD.org
          Reporter: jbeich at vfemail.net
                CC: x11 at FreeBSD.org

Created attachment 149304
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=149304&action=edit
incomplete fix

According fonts-conf(5) fontconfig uses cache in the form of <hash
value>-<architecture>.cache-<version>. And fc-cache(1) explicitly notes that
for every architecture a separate run is required. However, as
x11-fonts/linux-*-fontconfig tries to use native fontconfig it completely
ignores/predates architecture distinction in cache filenames.

Steps to reproduce:

1. install www/linux-firefox (or any port using linux-*-fontconfig)
2. install x11-fonts/noto (or any port invoking fc-cache)
3. start linux-firefox then quit it
4. notice ~/.cache/fontconfig or ~/.fontconfig now has files with the
   same hash as /var/db/fontconfig but for different architecture

Those directories may contain files:

  *-x86.cache-2 (linux-f10- i386)
  *-le32d4.cache-3 (linux-c6- i386)
  *-le64.cache-4 (native amd64)

In some cases ~/.cache expansion may be broken and `fontconfig' directory would
appear directly under $HOME.

x11@ is CC'd in case multilib infra ever materializes and they (not gnome@) own
Keywords/fc*ucl, so may help un-hardcode /compat/linux from the patch.

-- 
You are receiving this mail because:
You are on the CC list for the bug.