all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 53613@debbugs.gnu.org
Subject: [bug#53613] [PATCH] guix: Restore profile hook for TeX Live font maps.
Date: Tue, 01 Feb 2022 10:22:11 +0100	[thread overview]
Message-ID: <87r18n54cc.fsf@gnu.org> (raw)
In-Reply-To: <87pmo78p0r.fsf@elephly.net> (Ricardo Wurmus's message of "Tue, 01 Feb 2022 00:08:02 +0100")

Howdy!

Ricardo Wurmus <rekado@elephly.net> skribis:

[...]

> Unfortunately, this change threw out the font-map-sized baby with the
> texmf.cnf-infested bath water.  The effect of that was barely noticeable
> because font maps are weird and aren’t always used.  Besides, we had a
> couple of other font-related problems (e.g. invalid assumptions about
> directory links in kpathsea), which masked this newly introduced
> problem.
>
> This patch pulls the baby out of the drain: we’re again generating font
> maps (such as pdftex.map) based on the contents of the profile.

Oh, I see, makes perfect sense.

Should some of this go in the commit log?

[...]

> Does this really solve problems?  I don’t know.  I think it’s the right
> thing to do (and thus makes our modular TeX Live less wrong), but it
> didn’t solve mysteries like that koma-script bug that seems to be
> related to a missing font map file.  The koma-script bug remains because
> the font map file is ignored.

I didn’t see how the koma-script bug could relate to fonts but your
explanation at <https://issues.guix.gnu.org/33094> looks plausible to my
(untrained) eye.

Thanks for explaining and fixing this!

Ludo’.




  reply	other threads:[~2022-02-01  9:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-28 18:18 [bug#53613] [PATCH] guix: Restore profile hook for TeX Live font maps Ricardo Wurmus
2022-01-31 23:02 ` Ludovic Courtès
2022-01-31 23:08   ` Ricardo Wurmus
2022-02-01  9:22     ` Ludovic Courtès [this message]
2022-02-10 21:20       ` Ludovic Courtès
2022-02-10 21:39         ` bug#53613: " Ricardo Wurmus

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=87r18n54cc.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=53613@debbugs.gnu.org \
    --cc=rekado@elephly.net \
    /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.