From: zimoun <zimon.toutoune@gmail.com>
To: Jack Hill <jackhill@jackhill.us>
Cc: 50625@debbugs.gnu.org
Subject: bug#50625: ghostscript shell scripts refer to unqualified external commands
Date: Fri, 17 Sep 2021 16:44:54 +0200 [thread overview]
Message-ID: <CAJ3okZ387X0bWitCQfbWAMDmdBBtET7gduiqK+y8FqjeEs60LQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2109161121570.4243@marsh.hcoop.net>
Hi,
On Thu, 16 Sept 2021 at 17:29, Jack Hill <jackhill@jackhill.us> wrote:
> Many of the commands, e.g. ps2pdf, provided by the ghostscript package are
> implemented as shell scripts that do some argument or file name processing
> before invoking the main gs binary. These scripts invoke external commands
> like basename, awk, dirname, and even gs by dynamically looking them up
> PATH. Instead, they should refer to a specific path in the store so that
> the behavior of ghostscript doesn't depend on the environment and so that
> Guix can see these references.
Indeed.
--8<---------------cut here---------------start------------->8---
$ guix environment -C --ad-hoc ghostscript
[env]$ ps2pdf --version
/gnu/store/jc3x02w3dmbff7s5r7g2d21r2jswag4p-profile/bin/ps2pdf: line
8: dirname: command not found
/gnu/store/jc3x02w3dmbff7s5r7g2d21r2jswag4p-profile/bin/ps2pdf14: line
3: dirname: command not found
/gnu/store/jc3x02w3dmbff7s5r7g2d21r2jswag4p-profile/bin/ps2pdfwr: line
7: dirname: command not found
/gnu/store/jc3x02w3dmbff7s5r7g2d21r2jswag4p-profile/bin/ps2pdfwr: line
24: basename: command not found
Usage: [options...] (input.[e]ps|-) [output.pdf|-]
--8<---------------cut here---------------end--------------->8---
The fix would to add these external commands as 'inputs' and then let
'wrap-program'. Do you want to give a try?
Cheers,
simon
prev parent reply other threads:[~2021-09-17 14:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-16 15:28 bug#50625: ghostscript shell scripts refer to unqualified external commands Jack Hill
2021-09-17 14:44 ` zimoun [this message]
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=CAJ3okZ387X0bWitCQfbWAMDmdBBtET7gduiqK+y8FqjeEs60LQ@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=50625@debbugs.gnu.org \
--cc=jackhill@jackhill.us \
/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).