public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Masamichi Hosoda <trueroad@trueroad.jp>
To: cygwin@cygwin.com
Subject: libfontconfig-common-2.15.0-2 system font cache directory settings seem to be wrong
Date: Fri, 08 Mar 2024 21:53:10 +0900 (JST)	[thread overview]
Message-ID: <20240308.215310.2236687043088232299.trueroad@trueroad.jp> (raw)
In-Reply-To: <20240305221000.93449612424c65060193f63f@nifty.ne.jp>

Hi

If I understand correctly,
the system font cache directory setting in /etc/fonts/fonts.conf
provided by libfontconfig-common-2.15.0-2 is wrong.

In /etc/fonts/fonts.conf provided by libfontconfig-common-2.13.1-2

```
       <cachedir>/var/cache/fontconfig</cachedir>
```

So `fc-cache -s` creates system font cache files in `/var/cache/fontconfig`.
It is correct because `/var/cache` is a common system cache directory.

In /etc/fonts/fonts.conf provided by libfontconfig-common-2.15.0-2

```
       <cachedir>LOCAL_APPDATA_FONTCONFIG_CACHE</cachedir>
```

So `fc-cache -s` creates system font cache files
in `./LOCAL_APPDATA_FONTCONFIG_CACHE`.
`LOCAL_APPDATA_FONTCONFIG_CACHE` directory is created
in the *current* directory when fc-cache.
It is wrong because it means that
processes with different current directories have
different system font cache directories,
and the caches are no longer shared.

  reply	other threads:[~2024-03-08 12:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-05 11:48 libfontconfig-devel-2.15.0-1 links wrong DLL Masamichi Hosoda
2024-03-05 13:10 ` Takashi Yano
2024-03-08 12:53   ` Masamichi Hosoda [this message]
2024-03-08 13:23     ` libfontconfig-common-2.15.0-2 system font cache directory settings seem to be wrong Takashi Yano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240308.215310.2236687043088232299.trueroad@trueroad.jp \
    --to=trueroad@trueroad.jp \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).