From: Ricardo Wurmus <rekado@elephly.net>
To: guix-devel@gnu.org
Subject: wrap-program –> wrap-script
Date: Wed, 11 Dec 2019 16:57:41 +0100 [thread overview]
Message-ID: <87h8263le2.fsf@elephly.net> (raw)
Hi Guix,
I’ve just pushed a change to use wrap-script in one package. The
purpose of wrap-script is to wrap an executable without having to create
a separate wrapper shell script. It does this by prepending a Guile
script to the top of the file, which sets the environment variables and
then re-executes itself with the target interpreter (e.g. Python).
I noticed two things:
1) wrap-script does not automatically pull in Guile as a dependency, so
if Guile isn’t among the inputs it will create a bad shebang. This
should be fixed on core-updates.
2) we aren’t using wrap-script anywhere. I think a good use case would
be the Python build system’s “wrap” phase where we currently use
wrap-program. Most of the time we’d be dealing with Python scripts, so
using wrap-script would be more appropriate here.
What do you think?
--
Ricardo
next reply other threads:[~2019-12-11 15:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 15:57 Ricardo Wurmus [this message]
2019-12-13 15:07 ` wrap-program –> wrap-script Maxim Cournoyer
2019-12-17 10:57 ` Efraim Flashner
2019-12-17 12:10 ` Ricardo Wurmus
2019-12-19 16:19 ` Ludovic Courtès
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=87h8263le2.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
/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).