From: Nicolas Goaziou via Guix-patches via <guix-patches@gnu.org>
To: spencerpeters via Guix-patches via <guix-patches@gnu.org>
Cc: "rekado@elephly.net" <rekado@elephly.net>,
71602-done@debbugs.gnu.org, "andreas@enge.fr" <andreas@enge.fr>,
spencerpeters <spencerpeters@protonmail.com>
Subject: bug#71602: [PATCH] gnu: texlive-scripts: add mktexfmt
Date: Mon, 17 Jun 2024 09:18:59 +0200 [thread overview]
Message-ID: <87a5jkxcik.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CM8ctR0aIM2Hsd4u2h3ySzVLXZMdKdWGJP2dmR_jM_ZEvneWa_rPETFk5idr-dF1B6DsgzMGCK-i5okcq95lqPJ6G5PGAcGT69cZCRHbRyQ=@protonmail.com> (spencerpeters via Guix-patches via's message of "Sun, 16 Jun 2024 19:08:37 +0000")
Hello,
spencerpeters via Guix-patches via <guix-patches@gnu.org> writes:
> * gnu/packages/tex.scm (texlive-scripts): add mktexfmt
Good catch.
> Hello. I have noticed while using a modular TeX Live installation that the texlive-scripts package
> lacks mktexfmt, which is necessary for creating TeX fmts.
Actually, it is not strictly necessary. Guix uses "fmtutil-sys" to
generate such fmts. But you're right, the script should be installed anyway.
> #:link-scripts
> - (find-files "scripts")))))))))
> + (find-files "scripts"))))))
> + (add-after 'link-scripts 'link-mktexfmt
> + (lambda _
> + (let ((fmtutil (string-append #$output "/bin/fmtutil")))
> + (symlink fmtutil
> + (string-append #$output "/bin/mktexfmt" ))))))))
I integrated this in the `link-scripts' phase, and pushed to "tex-team"
branch. "mktexfmt" should be available once this branch is merged.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2024-06-17 7:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-16 19:08 [bug#71602] [PATCH] gnu: texlive-scripts: add mktexfmt spencerpeters via Guix-patches via
2024-06-17 7:18 ` Nicolas Goaziou via Guix-patches via [this message]
2024-06-30 11:34 ` Jorge Acereda
2024-06-30 14:32 ` Nicolas Goaziou via Guix-patches via
2024-06-30 16:47 ` Jorge Acereda
2024-06-30 17:10 ` Nicolas Goaziou via Guix-patches via
2024-06-30 17:49 ` Jorge Acereda
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=87a5jkxcik.fsf@nicolasgoaziou.fr \
--to=guix-patches@gnu.org \
--cc=71602-done@debbugs.gnu.org \
--cc=andreas@enge.fr \
--cc=mail@nicolasgoaziou.fr \
--cc=rekado@elephly.net \
--cc=spencerpeters@protonmail.com \
/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).