unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: Mark H Weaver <mhw@netris.org>,
	26877@debbugs.gnu.org, ng0 <ng0@pragmatique.xyz>
Subject: bug#26877: building fonts: fontcache must be updated regulary
Date: Sun, 10 Jul 2022 00:27:47 -0400	[thread overview]
Message-ID: <871quth9rw.fsf@gmail.com> (raw)
In-Reply-To: <8760h7nmec.fsf@gnu.org> ("Ludovic Courtès"'s message of "Thu, 11 May 2017 22:55:55 +0200")

Hello,

ludo@gnu.org (Ludovic Courtès) writes:

> Hi,
>
> Mark H Weaver <mhw@netris.org> skribis:
>
>> The usual Guix way to handle things like this is to arrange for the font
>> cache to be part of the profile, and to create a profile hook that
>> creates the cache from all of the built packages included within.
>
> The problem is that the cache should be mutable so that one can run
> “fc-cache -f” after having dropped files in ~/.local/share/fonts, for
> instance.
>
> That said, quite surprisingly, I think I never had to run ‘fc-cache’
> except in the situation above.

I've never had to do this in years, although I don't use "loose" fonts
manually installed under ~/.local/share/fonts.

Should we close the issue?  Our fontconfig package now honors fonts
found under XDG_DATA_DIRS, and it seems to just work.

Thanks,

Maxim




  reply	other threads:[~2022-07-10  4:28 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 [this message]
2023-08-11 10:06       ` 宋文武 via Bug reports for GNU Guix
2023-08-11 14:47         ` Maxim Cournoyer
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=871quth9rw.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=26877@debbugs.gnu.org \
    --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).