From: Philip McGrath <philip@philipmcgrath.com>
To: "(" <paren@disroot.org>, help-guix@gnu.org
Cc: help-guix@gnu.org, Kyle <kyle@posteo.net>
Subject: Re: Alternatives to --emulate-fhs on foreign distros
Date: Sun, 21 May 2023 00:32:33 -0400 [thread overview]
Message-ID: <4762300.cEBGB3zze1@bastet> (raw)
In-Reply-To: <C6AC89A1-423D-451B-93E4-60D14BA8C4AA@posteo.net>
[-- Attachment #1: Type: text/plain, Size: 915 bytes --]
On Friday, April 21, 2023 2:35:30 PM EDT Kyle wrote:
> Its kind of hard to test. The easiest I have managed has been to see that I
> don't get the error with --emulate-fhs in my call, and the script that
> fails starts with:
>
> #!/usr/bin/env txr
>
> To simplify things, I made a self contained txr script and wrapped that up
> in my test R package. Sure enough, after building the package I checked its
> store directory. Guix did not patch the path to the path to the env utility
> in that case.
Did you include txr as an input to your package? The 'patch-shebangs doesn't
patch in an absolute path to an env utility: it rewrites shebangs to use the
absolute path to the actual interpreter, in this case txr, and it only does so
if the interpreter is actually present at build time. (A package source might
contain scripts that aren't actually used, and they shouldn't create artificial
dependencies.)
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-05-21 4:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 6:18 Alternatives to --emulate-fhs on foreign distros Kyle Andrews
2023-04-19 8:08 ` Andreas Enge
2023-04-19 13:05 ` Martin Castillo
2023-04-19 15:10 ` (
2023-04-19 15:18 ` (
2023-04-19 17:24 ` Kyle
2023-04-19 18:30 ` (
2023-04-20 22:32 ` Kyle Andrews
2023-04-21 5:36 ` (
2023-04-21 18:35 ` Kyle
2023-04-21 18:57 ` Kyle
2023-05-21 4:32 ` Philip McGrath [this message]
2023-04-20 12:56 ` Maxim Cournoyer
2023-04-21 15:44 ` Kyle
2023-04-22 20:36 ` Maxim Cournoyer
2023-04-27 2:16 ` Kyle
2023-04-20 19:51 ` wolf
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=4762300.cEBGB3zze1@bastet \
--to=philip@philipmcgrath.com \
--cc=help-guix@gnu.org \
--cc=kyle@posteo.net \
--cc=paren@disroot.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.
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).