From: zimoun <zimon.toutoune@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
Ontje.Luensdorf@dlr.de, gwl-devel@gnu.org
Subject: Re: Problem with texlive-default-updmap.cfg
Date: Mon, 28 Feb 2022 12:01:18 +0100 [thread overview]
Message-ID: <CAJ3okZ1ZiBu7xR6SRE80SVH7k_1qVD+EbWWJgpNJN-Bb9aWBbQ@mail.gmail.com> (raw)
In-Reply-To: <87fso45hd6.fsf@elephly.net>
Hi,
On Sun, 27 Feb 2022 at 18:50, Ricardo Wurmus <rekado@elephly.net> wrote:
> > Not sure I understand the context well enough, but yes,
> > ‘texlive-font-maps’ in (guix profiles) uses packages from the host Guix,
> > not from an inferior (it cannot know that inferiors are being used).
> >
> > Does that lead it to build incorrect font maps or things like that?
>
> Worse: there’s a mismatch between what one Guix wants and what the other
> offers. Apparently the profile hook from the newer Guix is used, but
> the look up of texlive-default-updmap.cfg in (gnu packages tex) happens
> in the older Guix — which doesn’t *have* that package — and thus fails.
I do not understand all the machinery so it is probably irrelevant.
Is it not related to the recent improvements of inferiors? And the
recent texlive-default-updmap.cfg is just what spots out the flaw.
Cheers,
simon
next prev parent reply other threads:[~2022-02-28 11:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 9:37 Problem with texlive-default-updmap.cfg Ontje.Luensdorf
2022-02-23 15:08 ` Ricardo Wurmus
2022-02-23 22:15 ` Ricardo Wurmus
2022-02-27 17:32 ` Ludovic Courtès
2022-02-27 17:48 ` Ricardo Wurmus
2022-02-28 11:01 ` zimoun [this message]
2022-02-28 11:42 ` Ludovic Courtès
2022-02-28 13:17 ` Ricardo Wurmus
2022-02-28 13:15 ` Ricardo Wurmus
2022-03-30 12:32 ` Ricardo Wurmus
2022-03-31 6:31 ` Ontje.Luensdorf
2022-03-31 7:31 ` 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
List information: https://www.guixwl.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJ3okZ1ZiBu7xR6SRE80SVH7k_1qVD+EbWWJgpNJN-Bb9aWBbQ@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=Ontje.Luensdorf@dlr.de \
--cc=gwl-devel@gnu.org \
--cc=ludo@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.
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).