From: ng0 <ng0@pragmatique.xyz>
To: Mark H Weaver <mhw@netris.org>
Cc: 26877@debbugs.gnu.org, ng0 <ng0@pragmatique.xyz>
Subject: bug#26877: building fonts: fontcache must be updated regulary
Date: Thu, 11 May 2017 19:47:58 +0000 [thread overview]
Message-ID: <20170511194758.etpgtrboftdmptp4@abyayala> (raw)
In-Reply-To: <8760h7guba.fsf@netris.org>
Mark H Weaver transcribed 1.2K bytes:
> ng0 <ng0@pragmatique.xyz> writes:
>
> > The problem: Right now after just installing fonts, they do
> > not become available. This can lead to some applications
> > appearing "broken", etc. Other operating systems solve this
> > by having a post-install hook which roughly does just this.
> >
> > A possible solution:
> > Our fictional, not yet existing, font-build-system should
> > run "fc-cache --force --really-force",
>
> This cannot work, because the build system code is run within the build
> container, where it won't have access to anything in your home
> directory. Furthermore, for most users, the packages are built on
> another machine, namely one of our build farm slaves.
>
> Even the build system did somehow have access to your home directory,
> building the package is not the right time to run "fc-cache". On a
> multiuser system, if two users request the same derivation, it is only
> built for the first user, and the second user simply uses the one that
> the first user built. The relevant time to run "fc-cache" is when the
> font is _installed_ in your user profile.
>
> 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.
>
> Mark
>
Okay, you are right about the build system. Your approach reads
better, I was just looking for a way to start a discussion on
this. Right now it is not-obviously broken, and we need to fix
it at some point.
--
https://pragmatique.xyz
PGP: https://people.pragmatique.xyz/ng0/
next prev parent reply other threads:[~2017-05-11 19:49 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170511194758.etpgtrboftdmptp4@abyayala \
--to=ng0@pragmatique.xyz \
--cc=26877@debbugs.gnu.org \
--cc=mhw@netris.org \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.