From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Andy Tai <atai@atai.org>, guix-devel@gnu.org
Subject: Re: /bin/sh in package definitions
Date: Sun, 15 Jan 2023 08:41:38 +0100 [thread overview]
Message-ID: <0a762f95eba75124b91d2023b2c939251eb0c1bf.camel@gmail.com> (raw)
In-Reply-To: <CAJsg1E9AOV0MXKoyga5EApDMHd9uQ0uquMGF+JfLFqacjX6NAg@mail.gmail.com>
Am Freitag, dem 13.01.2023 um 15:40 -0800 schrieb Andy Tai:
> Hi, currently package definitions often need to patch references to
> /bin/sh as common in package sources or makefiles to make it refer to
> the actual bash shell used in Guix in /gnu/store/... somewhere.
>
> question 1: is there a way, to simulate /bin/sh using container or
> some such set up so the actual shell used by Guix can appear as
> /bin/sh in the package build process? (sorry if this is a wild
> question)
Yes, you can use /bin/sh in a container, but we deliberately set it up
so that it's not that inside a build container.
> question 2: (if question 1 is not possible) in guile, how to replace
> only occurrences of /bin/sh, not substring "/bin/sh" in some strings
> like /usr/bin/shsomethingsomethng, in the "patch" stage of package
> building?
Depends on your particular use case, but often, you could match e.g.
"/bin/sh" (including the quotes), or alternatively ^/bin/sh(.), where
depending on the thing matched via dot you either replace the
expression or leave it as-is.
Cheers
prev parent reply other threads:[~2023-01-15 7:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 23:40 /bin/sh in package definitions Andy Tai
2023-01-15 7:41 ` Liliana Marie Prikler [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=0a762f95eba75124b91d2023b2c939251eb0c1bf.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=atai@atai.org \
--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).