unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Emmanuel Beffara <manu@beffara.org>
Cc: Nicolas Goaziou <mail@nicolasgoaziou.fr>, guix-devel@gnu.org
Subject: Re: performance issue with TeX Live
Date: Wed, 11 Oct 2023 18:16:37 +0200	[thread overview]
Message-ID: <871qe1m8ro.fsf@elephly.net> (raw)
In-Reply-To: <20231010100449.GH894@beffara.org>


Emmanuel Beffara <manu@beffara.org> writes:

> De Nicolas Goaziou le 09/10/2023 à 16:03:
>> Emmanuel Beffara <manu@beffara.org> writes:
>> > 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.
>
> Ok, "unusable" may be an overstatement. But when compiling a simple document
> takes one or two minutes […]

Oh, that sounds bad.  I only ever use pretty small collections of TeX
Live packages, so I never noticed.

In the past we used to create a union directory and generated a
configuration file to only search for packages in that single directory
instead of searching a large number of directories.  I wonder if we
could do something like that.

-- 
Ricardo


  reply	other threads:[~2023-10-11 16:20 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
2023-10-10  8:04       ` Emmanuel Beffara
2023-10-11 16:16         ` Ricardo Wurmus [this message]
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=871qe1m8ro.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    --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).