From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: 64783@debbugs.gnu.org
Cc: isaac.vanbakel@inf.ethz.ch, dev@jpoiret.xyz
Subject: bug#64783: Build of texlive-font-maps fails
Date: Wed, 26 Jul 2023 16:34:04 +0200 [thread overview]
Message-ID: <87mszi3foj.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87sf9bytu3.fsf@jpoiret.xyz> (Josselin Poiret via Bug reports for's message of "Wed, 26 Jul 2023 10:12:36 +0200")
Hello,
Josselin Poiret via Bug reports for GNU Guix <bug-guix@gnu.org> writes:
> The `texlive` package contains the whole monolothic texlive
> distribution, and is different from the newer modular one. You probably
> want `texlive-bin` instead. `texlive-scheme-basic` is a meta-package
> propagating a basic set of tex packages that you might need.
Indeed, as suggested in the manual, one should install at least one
"scheme", or at least, a "collection", to use modular TeX Live.
Consequently, installing `texlive-bin' is not sufficient, and should be
avoided unless you want a very minimal system, with a lot of sweat. For
example, `texlive-bin' does not provide any ".fmt" file.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2023-07-26 15:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-22 5:04 bug#64783: Build of texlive-font-maps fails Dr. Arne Babenhauserheide
2023-07-22 23:53 ` Nicolas Goaziou
2023-07-27 6:30 ` Dr. Arne Babenhauserheide
2023-07-29 22:32 ` Nicolas Goaziou
2023-08-09 10:03 ` Dr. Arne Babenhauserheide
2023-08-09 16:30 ` Nicolas Goaziou
2023-08-09 17:54 ` Dr. Arne Babenhauserheide
2023-07-23 14:24 ` Dominik Riva via Bug reports for GNU Guix
2023-07-24 13:08 ` Isaac van Bakel
2023-07-26 8:12 ` Josselin Poiret via Bug reports for GNU Guix
2023-07-26 14:34 ` Nicolas Goaziou [this message]
2023-08-08 19:53 ` bug#64783: biber not in $PATH with texlive only Julian Flake
2023-08-09 16:32 ` Nicolas Goaziou
2023-08-10 7:15 ` Julian Flake
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=87mszi3foj.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=64783@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
--cc=isaac.vanbakel@inf.ethz.ch \
/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.