From: ludo@gnu.org (Ludovic Courtès)
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: 31850@debbugs.gnu.org, Ricardo Wurmus <rekado@elephly.net>
Subject: [bug#31850] [PATCH] gnu: texlive-bin: Use absolute path to ghostscript executable "gs".
Date: Sat, 16 Jun 2018 18:13:36 +0200 [thread overview]
Message-ID: <87lgbeogjz.fsf@gnu.org> (raw)
In-Reply-To: <20180615192622.6416-1-arunisaac@systemreboot.net> (Arun Isaac's message of "Sat, 16 Jun 2018 00:56:22 +0530")
Hello,
Arun Isaac <arunisaac@systemreboot.net> skribis:
> * gnu/packages/tex.scm (texlive-bin)[arguments]: Rename fix-unix-detection
> phase to configure-ghostscript-executable. Replace "gs" in epstopdf.pl with
> the absolute path to "gs" in the store.
LGTM.
> I seem to have made one of the lines way too long. I'll fix that before
> pushing, once someone has reviewed this patch. Also, should this patch
> go to core-updates considering that the texlive package is very tedious
> to build?
‘texlive-bin’ has just 252 dependent it seems, many of which are
‘texlive-’ packages, which are usually quickly built. So I’d say it’s
OK for master, but I could be missing some other way in which
‘texlive-bin’ is depended on. Ricardo, WDYT?
Ludo’.
next prev parent reply other threads:[~2018-06-16 16:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-15 19:26 [bug#31850] [PATCH] gnu: texlive-bin: Use absolute path to ghostscript executable "gs" Arun Isaac
[not found] ` <handler.31850.B.15290908242382.ack@debbugs.gnu.org>
2018-06-15 19:56 ` [bug#31850] Acknowledgement ([PATCH] gnu: texlive-bin: Use absolute path to ghostscript executable "gs".) Arun Isaac
2018-06-16 16:13 ` Ludovic Courtès [this message]
2018-06-16 20:46 ` [bug#31850] [PATCH] gnu: texlive-bin: Use absolute path to ghostscript executable "gs" Ricardo Wurmus
2018-06-17 7:06 ` Arun Isaac
2018-06-17 11:44 ` Ricardo Wurmus
2018-06-17 16:01 ` bug#31850: " Arun Isaac
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=87lgbeogjz.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=31850@debbugs.gnu.org \
--cc=arunisaac@systemreboot.net \
--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.