From: Christopher Baines <mail@cbaines.net>
To: Thomas Danckaert <post@thomasdanckaert.be>
Cc: 28660@debbugs.gnu.org
Subject: [bug#28660] [PATCH] gnu: python-numpy: Give sh store location instead of setting $SHELL.
Date: Wed, 4 Oct 2017 07:30:48 +0100 [thread overview]
Message-ID: <20171004073048.1187465b@cbaines.net> (raw)
In-Reply-To: <20171001.144404.698351802734865623.post@thomasdanckaert.be>
[-- Attachment #1: Type: text/plain, Size: 976 bytes --]
On Sun, 01 Oct 2017 14:44:04 +0200 (CEST)
Thomas Danckaert <post@thomasdanckaert.be> wrote:
> Hi Guix,
>
> I slightly botched the last numpy update: setting $SHELL works, but
> then we have to set $SHELL for every package which uses numpy's
> distutils. I don't know how many packages there are, but it includes
> scipy and python-hdf (and therefore those builds are currently broken
> on master...).
>
> The attached patch should fix the issue for all packages, by setting
> the default shell to the “/bin/sh” of the build environment's bash
> package (i.e. bash-minimal).
Could bash be specified as an input, and that used instead? This would
mean that the behaviour of the package is more isolated from the
environment.
For example, on non GuixSD systems, /bin/sh could be something other
than bash. But, if the numpy package depends on some bash in the store,
and uses that, then it would be isolated from this.
What do you think?
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 963 bytes --]
next prev parent reply other threads:[~2017-10-04 6:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-01 12:44 [bug#28660] [PATCH] gnu: python-numpy: Give sh store location instead of setting $SHELL Thomas Danckaert
2017-10-04 6:30 ` Christopher Baines [this message]
2017-10-04 7:04 ` Thomas Danckaert
2017-10-04 7:49 ` Christopher Baines
2017-10-04 12:12 ` bug#28660: " Thomas Danckaert
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=20171004073048.1187465b@cbaines.net \
--to=mail@cbaines.net \
--cc=28660@debbugs.gnu.org \
--cc=post@thomasdanckaert.be \
/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.