From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Emmanuel Beffara <manu@beffara.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: performance issue with TeX Live
Date: Mon, 09 Oct 2023 16:03:14 +0200 [thread overview]
Message-ID: <87fs2jx599.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <20231009111109.GH1344@beffara.org> (Emmanuel Beffara's message of "Mon, 9 Oct 2023 11:11:09 +0200")
Hello,
Emmanuel Beffara <manu@beffara.org> writes:
> De Nicolas Goaziou le 13/09/2023 à 14:39:
>> It may be interesting to compare location and contents of the ls-R files
>> in both installations.
>
> I tried to explore this but I see no reason why the ls-R files would be
> ignored
I spent some time exploring this, but I cannot tell either. Though, it
is plausible that the problem is related to ls-R files, or, more
accurately, the reason why they are not read.
Note that those files are not installed in every tree. For example
`texlive-updmap.cfg' doesn't create any so, IIUC, any TeX Live tree used
as a build input require to navigate the file system.
I also tried to tweak TEXMFDBS and TEXMF values in "texmf.cnf" from
"texlive-libkpathsea" package, but couldn't find a sweet spot.
At the moment, I'm running out of ideas, and time.
> I do want to contribute to a solution, because right now texlive is
> practically unusable in Guix.
FWIW, I use modular TeX Live regularly, so "unusable" is probably a bit
strong. However, I agree the current situation is frustrating.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2023-10-09 14:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 15:54 performance issue with TeX Live Emmanuel Beffara
2023-09-12 17:11 ` Olivier Dion
2023-09-13 12:42 ` Emmanuel Beffara
2023-09-13 12:39 ` Nicolas Goaziou
2023-10-09 9:11 ` Emmanuel Beffara
2023-10-09 14:03 ` Nicolas Goaziou [this message]
2023-10-10 8:04 ` Emmanuel Beffara
2023-10-11 16:16 ` Ricardo Wurmus
2023-10-14 16:06 ` Maxim Cournoyer
2023-10-16 12:22 ` Emmanuel Beffara
2023-10-16 13:46 ` Maxim Cournoyer
2023-10-16 15:16 ` Emmanuel Beffara
2023-10-16 16:23 ` 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=87fs2jx599.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=guix-devel@gnu.org \
--cc=manu@beffara.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 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).