unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: 宋文武 <iyzsong@envs.net>
Cc: "Mark H Weaver" <mhw@netris.org>,
	"Ludovic Courtès" <ludo@gnu.org>, ng0 <ng0@pragmatique.xyz>,
	26877-done@debbugs.gnu.org
Subject: bug#26877: building fonts: fontcache must be updated regulary
Date: Fri, 11 Aug 2023 10:47:17 -0400	[thread overview]
Message-ID: <878rahfxfu.fsf@gmail.com> (raw)
In-Reply-To: <87350pdhb3.fsf@envs.net> ("宋文武"'s message of "Fri, 11 Aug 2023 18:06:24 +0800")

Hello,

宋文武 <iyzsong@envs.net> writes:

[...]

> Hello, I think we can close this now, since this commit:
>
> commit 6f12880a76a6c91058718d15845f8b9d9b529a5a
> Author: Sarah Morgensen <iskarian <at> mgsn.dev>
> Date:   Fri Jun 18 17:52:05 2021 -0700
>
>     gnu: fontconfig: Use (locally) deterministic caching
>     
>     Make fontconfig use directory contents rather than modification time to
>     determine cache validity (by pretending that mtime is broken).
>
> There is no need to run 'fc-cache' manually, and applications just need
> close/restart to use newly install fonts (also manual run here doesn't
> remove the need of restart).

Excellent, I had forgotten about that commit.  Thanks to Sarah for
fixing the issue!

Closing.

-- 
Thanks,
Maxim




  reply	other threads:[~2023-08-11 14:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-11  8:36 bug#26877: building fonts: fontcache must be updated regulary ng0
2017-05-11 17:46 ` Mark H Weaver
2017-05-11 19:47   ` ng0
2017-05-11 20:55   ` Ludovic Courtès
2022-07-10  4:27     ` Maxim Cournoyer
2023-08-11 10:06       ` 宋文武 via Bug reports for GNU Guix
2023-08-11 14:47         ` Maxim Cournoyer [this message]
2019-07-07 10:49 ` bug#26877: Fontcache in system profile not updated John Soo

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=878rahfxfu.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=26877-done@debbugs.gnu.org \
    --cc=iyzsong@envs.net \
    --cc=ludo@gnu.org \
    --cc=mhw@netris.org \
    --cc=ng0@pragmatique.xyz \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).