unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Nils Gillmann <ng0@n0.is>
To: "Gábor Boskovits" <boskovits@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Environment variables in Guix and GuixSD
Date: Fri, 9 Nov 2018 13:49:43 +0000	[thread overview]
Message-ID: <20181109134943.rmx24nlmxo4wxiu6@abyayala> (raw)
In-Reply-To: <CAE4v=ph3C+wAKpnWGPz9VexiC0ZRqXJxJMriJNy4AGarDRwr_w@mail.gmail.com>

Gábor Boskovits transcribed 3.2K 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.

But you are just scratching on the surface. As I noted long time ago,
the file itself is bash specific. To have bash in there makes sense as
the project was and is Bash focused. For other shells you end up
either maintaining your own codebase or constructing bash->YOUR_SHELL
translators.

If anything it makes sense to throw (part of) this into /etc/bash/,
which at least on Gentoo is the way to define systemwide data for
Bash.

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

  reply	other threads:[~2018-11-09 13:48 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
2018-11-09 13:49         ` Nils Gillmann [this message]
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

  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=20181109134943.rmx24nlmxo4wxiu6@abyayala \
    --to=ng0@n0.is \
    --cc=boskovits@gmail.com \
    --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).