unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Thiago Jung Bauermann <bauermann@kolabnow.com>
To: guix-devel@gnu.org
Subject: [core-updates] texlive 2021 bootstrap problem
Date: Tue, 15 Jun 2021 16:00:51 -0300	[thread overview]
Message-ID: <3693876.osayq9kAQP@popigai> (raw)

Hello,

In an attempt to verify whether bug 48064¹ (”texlive-* packages fail to 
build non-deterministically”) is fixed by the current TeX Live version, I’ve 
been working on updating it to version 2021.1².

Unfortunately I ran into a bootstrapping issue: texlive-latex-base now 
depends on texlive-latex-l3kernel, otherwise its build fails with:

LaTeX2e <2020-10-01> patch level 4
! LaTeX requires expl3.

The problem is that if I add texlive-latex-l3kernel to the propagated-
inputs list of texlive-latex-base, then a dependency loop is formed since 
texlive-latex-l3kernel uses the texlive-build-system, which adds texlive-
latex-base as an implicit input. And if I understand thing correctly, 
l3kernel does indeed need some form of TeX or LaTeX in order to run
`source/latex/l3kernel/l3.ins`.

I tried to “cheat” and added the build argument
`#:texlive-latex-base ,texlive-bin` to texlive-latex-l3kernel (since 
texlive-bin doesn’t depend on texlive-latex-base), but then I get an error 
about not being able to find `luatex.fmt`.

Looking around the web, I found this answer:

> To answer your question about deactivation ... the L3 programming layer 
> is part of the core LaTeX format since release 2019-10-01 and it can't be 
> deactivated. At the moment it is there to speed up processing of packages 
> written in expl3, e.g., xparse, fontspec, and many others, but going 
> forward core parts of LaTeX will make direct use of it.
> 
> Deactivation is only possible by using a release prior to 2019-10 (even 
> rollback via "latexrelease" will load).
https://tex.stackexchange.com/a/538716

Does anyone have an idea how to break this dependency loop? Do we need to 
have a package definition for a pre-2019-10 version of LaTeX just to build 
texlive-latex-l3kernel, and then use that as a dependency for the actual 
texlive-latex-base package?

The only alternative I can think of is trying to build a minimal version of 
2021.1 LaTeX which somehow doesn’t use expl3 so that it can be used to 
build texlive-latex-l3kernel. But that is above my very superficial 
understanding of TeX and LaTeX. And the quote I pasted above doesn’t look 
very encouraging.

If anyone wants to have a look at what I have so far, I pushed my patch to 
branch “bug-48064-texlive-2021” at https://gitlab.com/bauermann/guix .

-- 
Thanks,
Thiago


¹ https://issues.guix.gnu.org/48064
² Well, almost. In order to have a stable URL to fetch from, I’m using the 
latest version available in the historic repository, which is slightly 
older than 2021.1.





             reply	other threads:[~2021-06-16 12:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-15 19:00 Thiago Jung Bauermann [this message]
2021-06-22  0:43 ` [core-updates] texlive 2021 bootstrap problem Thiago Jung Bauermann
2021-06-24 18:26   ` Maxim Cournoyer
2021-06-24 20:53     ` Thiago Jung Bauermann
2021-06-25  3:34       ` Maxim Cournoyer
2021-06-25  5:00         ` Thiago Jung Bauermann
2021-06-29 20:43           ` Thiago Jung Bauermann
2021-06-30 16:21             ` Maxim Cournoyer
2021-07-05  0:24               ` Thiago Jung Bauermann

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=3693876.osayq9kAQP@popigai \
    --to=bauermann@kolabnow.com \
    --cc=guix-devel@gnu.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).