[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Problem with texlive-default-updmap.cfg
From: |
Ludovic Courtès |
Subject: |
Re: Problem with texlive-default-updmap.cfg |
Date: |
Mon, 28 Feb 2022 12:42:55 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) |
Hi,
Ricardo Wurmus <rekado@elephly.net> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
[...]
>>> The profile hook does perform a lazy package lookup with this:
>>>
>>> (define updmap.cfg
>>> (module-ref (resolve-interface '(gnu packages tex))
>>> 'texlive-default-updmap.cfg))
>>>
>>> I wonder if that ends up being evaluated outside of the inferior
>>> somehow. That would be quite a bummer.
>>
>> 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.
You mean the ‘module-ref’ above happens in the inferior’s module?
That’s not possible, unless there’s some extra load path trickery going
on.
Do you have a simple reproducer?
Thanks,
Ludo’.