From: ludo@gnu.org (Ludovic Courtès)
To: Axel <grafov@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: zsh and fish missed in /etc/shells?
Date: Thu, 12 Mar 2015 21:29:21 +0100 [thread overview]
Message-ID: <87vbi60xjy.fsf@gnu.org> (raw)
In-Reply-To: <CAJpGxxCmP6-H0U53wv-q2v_VMBzYfAY427M4kadcqTvLMxdHXA@mail.gmail.com> (Axel's message of "Wed, 11 Mar 2015 15:42:32 +0300")
Axel <grafov@gmail.com> skribis:
> Well, I modified the patch and now it just trivially add paths for
> fish, tcsh and zsh.
>
> For example Debian has add-shell/remove-shell scripts triggered on
> package installing and removing. FTP servers like proftpd by default
> check for installed shells and with this patch they will allow for a
> user shells that don't really exist in a system. Probably it is not a
> problem though.
I think it’s fine.
> I noted in a changelog what we add paths unconditionally.
I moved this explanation as a comment in the code itself; we only
mention in change logs the actual changes, and explanations usually go
to comments (info "(standards) Change Logs").
> From d17569a3b3f00066531361b9f29b840be2444982 Mon Sep 17 00:00:00 2001
> From: "Alexander I.Grafov (Axel)" <grafov@gmail.com>
> Date: Wed, 11 Mar 2015 15:17:24 +0300
> Subject: [PATCH] system: Add fish/tcsh/zsh to /etc/shells
>
> * gnu/system.scm (etc-directory): Add fish, tcsh and zsh paths
> to /etc/shells. We don't check that these shells really installed.
Applied, thanks!
Ludo’.
prev parent reply other threads:[~2015-03-12 20:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 2:33 zsh and fish missed in /etc/shells? Axel
2015-03-09 8:59 ` Ludovic Courtès
2015-03-10 22:30 ` Axel
2015-03-10 23:49 ` Axel
2015-03-11 9:43 ` Ludovic Courtès
2015-03-11 12:42 ` Axel
2015-03-12 20:29 ` Ludovic Courtès [this message]
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=87vbi60xjy.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=grafov@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 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.