unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: 30435@debbugs.gnu.org, guix-devel@gnu.org, hmk <hmk42@posteo.de>
Subject: Re: bug#30435: libreoffice: Fonts don't show up after install
Date: Thu, 02 Apr 2020 17:46:00 +0200	[thread overview]
Message-ID: <875zehopqf.fsf@gnu.org> (raw)
In-Reply-To: <87a73ui78x.fsf@ambrevar.xyz> (Pierre Neidhardt's message of "Thu, 02 Apr 2020 11:09:34 +0200")

Hi,

Pierre Neidhardt <mail@ambrevar.xyz> skribis:

> Running
>
> fc-cache -fv
>
> fixes the issue.
>
> Should we run this command in a profile hook?

Profile hooks are normal derivations; as such, they don’t have access to
anything but their dependencies and their output(s).

There’s currently no infrastructure to run arbitrary code upon package
installation (which I think is a feature more than a bug :-)).  We could
make an exception, but it’s kinda ugly.

I wonder if, instead, we could have Fontconfig realize that the cache is
stale somehow.

Alternately, we could generate the cache in a profile hook and have
Fontconfig use that cache instead of the one in ~/.cache.  However,
Fontconfig would need to be able to:

  1. Be told which cache to use, not just the one from ~/.guix-profile,
     so that it works equally well with other profiles.

  2. Merge several caches, so it can also account for fonts installed in
     /run/current-system/profile.

We discussed all this several times in the past but I don’t think it
went further.

Ludo’.

  parent reply	other threads:[~2020-04-02 15:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bad1fc034ed4a0a4dbf14f74d431b7ae@posteo.de>
2020-04-02  9:09 ` bug#30435: libreoffice: Fonts don't show up after install Pierre Neidhardt
2020-04-02  9:19   ` Nicolò Balzarotti
2020-04-02  9:37     ` John Soo
2020-04-02 15:47     ` Ludovic Courtès
2020-04-02 15:46   ` Ludovic Courtès [this message]
2020-04-02 15:59     ` Pierre Neidhardt
2023-02-20 16:05     ` Maxim Cournoyer
2023-02-20 17:32       ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-02-20 18:22         ` Maxim Cournoyer

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=875zehopqf.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=30435@debbugs.gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=hmk42@posteo.de \
    --cc=mail@ambrevar.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).