all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Gábor Boskovits" <boskovits@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Environment variables in Guix and GuixSD
Date: Thu, 8 Nov 2018 08:02:41 +0100	[thread overview]
Message-ID: <CAE4v=ph3C+wAKpnWGPz9VexiC0ZRqXJxJMriJNy4AGarDRwr_w@mail.gmail.com> (raw)
In-Reply-To: <87a7mksgcl.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1015 bytes --]

Hello Ludo,

2018. nov. 7., Sze 22:55 dátummal Ludovic Courtès <ludo@gnu.org> ezt írta:

> Hi,
>
> Gábor Boskovits <boskovits@gmail.com> skribis:
>
> > I have seen in the /etc/profile file that it suggest you to do something
> like
> >
> > source $GUIX_PROFILE/etc/profile.
>
> Right, you see this advice in $GUIX_PROFILE/etc/profile itself.
>
> > This causes problems on systems where the startup file is executed by
> > a posix /bin/sh, as this is bash specific.
>
> $GUIX_PROFILE/etc/profile is not honored by any shell.  One has to
> specifically put the ‘source’ line above in whichever file is
> appropriate (~/.bash_profile, ~/.profile, /etc/profile, etc.)
>

I did not express myself cleanly. What my problem was that 'source' is bash
specific, while we can use '.' in posix shells.


> On GuixSD this happens automatically but on a foreign distro users have
> to add the ‘source’ line somewhere.
>
> Does that make sense?
>
> Thanks,
> Ludo’.
>
g_bor

>

[-- Attachment #2: Type: text/html, Size: 1839 bytes --]

  reply	other threads:[~2018-11-08  7:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-04  7:13 Environment variables in Guix and GuixSD swedebugia
2018-11-06 11:32 ` Ludovic Courtès
2018-11-06 11:38   ` Gábor Boskovits
2018-11-07 21:55     ` Ludovic Courtès
2018-11-08  7:02       ` Gábor Boskovits [this message]
2018-11-09 13:49         ` Nils Gillmann
2018-11-11 13:26         ` Ludovic Courtès

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='CAE4v=ph3C+wAKpnWGPz9VexiC0ZRqXJxJMriJNy4AGarDRwr_w@mail.gmail.com' \
    --to=boskovits@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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.