all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Thomas Danckaert <post@thomasdanckaert.be>
To: mail@cbaines.net
Cc: 28660@debbugs.gnu.org
Subject: [bug#28660] [PATCH] gnu: python-numpy: Give sh store location instead of setting $SHELL.
Date: Wed, 04 Oct 2017 09:04:36 +0200 (CEST)	[thread overview]
Message-ID: <20171004.090436.431865073991228123.post@thomasdanckaert.be> (raw)
In-Reply-To: <20171004073048.1187465b@cbaines.net>

From: Christopher Baines <mail@cbaines.net>
Subject: Re: [bug#28660] [PATCH] gnu: python-numpy: Give sh store 
location instead of setting $SHELL.
Date: Wed, 4 Oct 2017 07:30:48 +0100

> 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.

Sounds good, but I'm afraid I don't understand what you mean (maybe 
it's still too early in the morning).  If we add a "bash" to the 
package inputs, it will still come from the store.  So probably you 
mean something else by “specified as an input”?

> 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.

That's true, though users on such systems could set $SHELL to 
override the default one from the store.  But maybe avoiding having 
to do that is what you mean by “more isolated from the environment”?

The shell is used for very limited purposes anyway (essentially to 
run C and Fortran compilers to build extenstions, AFAIU), but I'm 
happy to improve the patch if it's useful.  If you have a solution 
that allows users to use their own /bin/sh if they want, but still 
works for all builds of dependent packages on Guix, please explain :-)

Thomas

  reply	other threads:[~2017-10-04  7:05 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
2017-10-04  7:04   ` Thomas Danckaert [this message]
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=20171004.090436.431865073991228123.post@thomasdanckaert.be \
    --to=post@thomasdanckaert.be \
    --cc=28660@debbugs.gnu.org \
    --cc=mail@cbaines.net \
    /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.