all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: "Cook, Malcolm" <MEC@stowers.org>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>,
	"'bio-packaging@mailman.open-bio.org'"
	<bio-packaging@mailman.open-bio.org>
Subject: Re: Making the case for GNU Guix ... advice sought
Date: Sun, 28 Feb 2016 14:52:28 +0100	[thread overview]
Message-ID: <877fhpvt5v.fsf@gnu.org> (raw)
In-Reply-To: <3125026547a945d28d1b32f57594c4d7@exchsrv2.sgc.loc> (Malcolm Cook's message of "Thu, 18 Feb 2016 23:29:49 +0000")

"Cook, Malcolm" <MEC@stowers.org> skribis:

> What is not clear to me is whether bash is assumed elsewhere in guix.... for instance, the fact that 
>
> 	guix package --search-paths
>
> reports environment variables in bash syntax.

In practice it’s almost plain Bourne shell syntax.  I think the only
“Bashism” is the mixed assignment and export (“export VAR=value”), which
is supported by most Bourne-compatible shells I believe (Dash being an
exception.)

> Any insights here?

The ‘etc/profile’ file that is created within profiles, such as
~/.guix-profile/etc/profile, uses the same syntax as above.

I don’t think there are other places in the user interfaces where Bash
is expected.

Thanks,
Ludo’.

  parent reply	other threads:[~2016-02-28 13:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-08 19:43 Making the case for GNU Guix ... advice sought Cook, Malcolm
2016-02-09 15:03 ` Ricardo Wurmus
2016-02-09 19:54   ` Leo Famulari
2016-02-09 20:27     ` Ludovic Courtès
2016-02-09 20:30   ` Ludovic Courtès
2016-02-18 23:29   ` Cook, Malcolm
2016-02-19 10:10     ` Pjotr Prins
2016-02-19 15:06       ` Cook, Malcolm
2016-02-28 13:52     ` Ludovic Courtès [this message]
2016-02-28 14:42     ` Ricardo Wurmus
2016-02-29 16:55       ` Cook, Malcolm
2016-02-29 17:10         ` Cook, Malcolm
2016-03-01 21:22           ` Ludovic Courtès
2016-02-09 20:36 ` Ludovic Courtès
2016-02-10 16:01   ` Cook, Malcolm
2016-02-18 23:26     ` Cook, Malcolm

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=877fhpvt5v.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=MEC@stowers.org \
    --cc=bio-packaging@mailman.open-bio.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 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.