From: Chris Marusich <cmmarusich@gmail.com>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: guix-devel@gnu.org
Subject: Re: User shell: state or config?
Date: Thu, 25 Apr 2019 23:25:20 -0700 [thread overview]
Message-ID: <87r29pb7vz.fsf@gmail.com> (raw)
In-Reply-To: <87sgu60xor.fsf@nckx> (Tobias Geerinckx-Rice's message of "Thu, 25 Apr 2019 20:03:32 +0200")
[-- Attachment #1: Type: text/plain, Size: 732 bytes --]
Tobias Geerinckx-Rice <me@tobias.gr> writes:
>> All in all, I’m in favor of switching back to the previous behavior:
>> considering user shells as system config. That’s a one-line change
>> in
>> (gnu build accounts).
>
> +1!
+1 from me as well. Allowing the shell to be declaratively defined in
the system config, but also allowing a user to override it permanently
at runtime via chsh, seems like a nice middle ground between treating it
as "config" vs. "state".
I think in Guix System it is generally better to treat as much as
possible as "config". After all, Guix System is basically an exercise
in extending the functional software deployment model to whole-system
management, right?
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-04-26 6:25 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 [this message]
2019-04-27 10:51 ` Ludovic Courtès
2019-04-26 20:18 ` Tanguy Le Carrour
2019-04-27 10:54 ` Ludovic Courtès
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=87r29pb7vz.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=guix-devel@gnu.org \
--cc=me@tobias.gr \
/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).