unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: Felix Lechner via "Development of GNU Guix and the GNU System
	distribution." <guix-devel@gnu.org>
Cc: Felix Lechner <felix.lechner@lease-up.com>
Subject: Re: Thoughtful updates to TexLive
Date: Sat, 26 Oct 2024 10:36:41 +0200	[thread overview]
Message-ID: <87ed43mfae.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87bjz7eken.fsf@lease-up.com> (Felix Lechner via's message of "Fri, 25 Oct 2024 18:13:20 -0700")

Hello,

Felix Lechner writes:

> Should updates to TexLive or its prerequisites fall under the
> core-updates policy (or whatever its successor is)?
>
> My Guix is heavily modified and building TexLive takes an hour and a
> half.  Grafting it takes nearly as long.  Thanks!

What TexLive are you talking about? There are two TeX Live distributions
in Guix: the monolithic one, i.e., `texlive', and the modular one, i.e.,
the set of all `texlive-*' packages.

Monolithic TeX Live is not substitutable so no matter how heavily
modified your Guix is, you will always rebuild it at every dependency
change.

My suggestion is to use modular TeX Live with a reasonable set of
packages. I.e., you certainly don't need to pull `texlive-scheme-full',
the modular counterpart of `texlive'.


Regards,
-- 
Nicolas Goaziou




      reply	other threads:[~2024-10-26  8:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-26  1:13 Thoughtful updates to TexLive Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-10-26  8:36 ` Nicolas Goaziou via Development of GNU Guix and the GNU System distribution. [this message]

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=87ed43mfae.fsf@nicolasgoaziou.fr \
    --to=guix-devel@gnu.org \
    --cc=felix.lechner@lease-up.com \
    --cc=mail@nicolasgoaziou.fr \
    /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).