unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Tanguy Le Carrour <tanguy@bioneland.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: User shell: state or config?
Date: Sat, 27 Apr 2019 12:54:15 +0200	[thread overview]
Message-ID: <87h8ajiuqw.fsf@gnu.org> (raw)
In-Reply-To: <20190426201818.4vw3ycp6ep4i3zjd@melmoth> (Tanguy Le Carrour's message of "Fri, 26 Apr 2019 22:18:18 +0200")

Hi,

Tanguy Le Carrour <tanguy@bioneland.org> skribis:

> I don't yet understand the consequences of this choice, so I don't have an
> opinion on this. For instance, I don't yet understand why, on my system, two
> shells installed "system wide" with `guix system reconfigure`
> (namely bash and fish) don't have the same "type" of path [1]?
> I was expecting fish to be in the `/run/current-system/profile/bin/`
> folder. And what about the second bash?!
>
> [1]: from `/etc/shells`
>      /run/current-system/profile/bin/bash
>      /gnu/store/qn1ax1fkj16x280m1rv7mcimfmn9l2pf-bash-4.4.23/bin/bash
>      /gnu/store/9r5z8k0p0ilmg8qfyc82x11ybacawfqa-fish-3.0.2/bin/fish

/etc/shells is one of these good ol’ Unix hacks, like /etc/fstab, that
don’t make much sense on Guix, but that we provide to please a number of
programs that rely on it (in this case: xterm and polkit, notably, and
chsh.)

You can find in (gnu system shadow) the code that creates this file.
The first three lines are added systematically, while the others are
derived from user accounts.

HTH,
Ludo’.

  reply	other threads:[~2019-04-27 10:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-25 10:40 User shell: state or config? Ludovic Courtès
2019-04-25 11:59 ` mikadoZero
2019-04-25 18:03   ` Tobias Geerinckx-Rice
2019-04-26  6:25     ` Chris Marusich
2019-04-27 10:51       ` Ludovic Courtès
2019-04-26 20:18 ` Tanguy Le Carrour
2019-04-27 10:54   ` Ludovic Courtès [this message]
2019-04-27  8:22 ` Meiyo Peng

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=87h8ajiuqw.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=tanguy@bioneland.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).