all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: 63604@debbugs.gnu.org
Cc: rekado@elephly.net
Subject: [bug#63604] Branch "tex-team-next" in need of review
Date: Wed, 14 Jun 2023 11:24:16 +0200	[thread overview]
Message-ID: <87v8fq9z27.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87r0qod1gh.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Tue, 06 Jun 2023 18:01:34 +0200")

Here's another update for tex-team-next branch.

The biggest change is the removal of `texlive-base' and
`texlive-latex-base' packages, which do not exist as TeX Live packages.
They are replaced by, respectively, `texlive-scheme-basic' and
`texlive-latex-bin'.

Consequently, the `#:texlive-latex-base' argument no longer exists. It
is replaced by `#:texlive-latex-bin?'. The importer automatically set it
to #f when necessary.

I also started to introduce collections and schemes from TeX Live.  At
this point, the following command,

  ./pre-inst-env guix shell --pure texlive-scheme-basic texlive-babel-french -- latex /tmp/test.tex

can compile the following LaTeX document without any hyphenation warning:

--8<---------------cut here---------------start------------->8---
\documentclass{article}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage[french]{babel}
\begin{document}
Success!
\end{document}
--8<---------------cut here---------------end--------------->8---

> So, what's next?
>
> - Install executables (copied from `texlive-bin') along with the texlive
>   package, when appropriate. The more packages you install, the less you
>   need `texlive-bin'. Ultimately, I want to get rid of `texlive-bin' as
>   a native input for every package. I think it should be limited to the
>   first few packages needed to build the rest. If that works, the
>   #:texlive-bin keyword can go away.

I admit that plan failed. Many binaries are tightly bound to each other.
I couldn't extract each of them and associate them to the right package.

It would be possible, however, to split `texlive-bin' into multiple
independent outputs (as NixOS does) in order to reduce the size of TeX
Live packages. Regarding that size, there's also the issue (at least it
seems to me) that `texlive-bin' retains a reference to GCC.

I won't look into any of the above in the current "tex-team-next"
branch.

> - Replace `texlive-latex-base', which doesn't exist in TeX Live, with
>   `texlive-latex-bin'.  Consequently, `#:texlive-latex-base' would be
>   renamed `#:texlive-latex-bin'.

Done.

> - Limit propagated inputs to the bare minimum, as defined in Tex Live,
>   and, at the same time, introduce collections and schemes. For example,
>   `texlive-scheme-basic' would replace `texlive-base'.

I started this. Since I need to review each package to reduce propagated
inputs, I may as well consider updating TeX Live to a more recent
release first. I'll see if I can do this during the next days.
Unfortunately, building `texlive-bin' takes a long time.

Feedback welcome.

Regards,




  reply	other threads:[~2023-06-14  9:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-20  9:38 [bug#63604] Branch "tex-team-next" in need of review Nicolas Goaziou
2023-05-21 16:27 ` Nicolas Goaziou
2023-05-28  6:38 ` Nicolas Goaziou
2023-06-06 16:01   ` Nicolas Goaziou
2023-06-14  9:24     ` Nicolas Goaziou [this message]
2023-06-29  9:14       ` Nicolas Goaziou
2023-08-27  8:37 ` [bug#63604] Closing? Andreas Enge
2023-08-27  9:42   ` bug#63604: Closing? Nicolas Goaziou

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87v8fq9z27.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=63604@debbugs.gnu.org \
    --cc=rekado@elephly.net \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.