From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: xterm: Accept $SHELL even if not in /etc/shells
Date: Fri, 14 Feb 2014 11:59:32 +0100 [thread overview]
Message-ID: <87r4763qp7.fsf@gnu.org> (raw)
In-Reply-To: <87ha83m0wg.fsf@netris.org> (Mark H. Weaver's message of "Thu, 13 Feb 2014 11:29:35 -0500")
Mark H Weaver <mhw@netris.org> skribis:
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Mark H Weaver <mhw@netris.org> skribis:
>>
>>> IMO, it's not reasonable to have to add
>>> /home/<USER>/<PROFILE>/bin/<SHELL> for every combination of <USER>,
>>> <PROFILE>, and <SHELL> to /etc/shells, in order to prevent 'xterm' from
>>> overriding your $SHELL setting.
>>
>> On NixOS, /etc/shells contains this:
>>
>> /run/current-system/sw/bin/bash
>> /var/run/current-system/sw/bin/bash
>> /bin/sh
>>
>> Where {/var/,}/run/current-system contains the “global” profile, like on
>> our QEMU images.
>>
>> Perhaps that’s good enough no?
>
> If a user wants to set $SHELL to be the one in their private profile,
> I think 'xterm' shouldn't ignore it and modify $SHELL just because it
> hasn't been authorized by the administrator of the system.
Agreed.
However, we’re just packaging an existing application. IMO, when we
find such limitations (it’s really a limitation, and not something that
makes it completely unusable), we should submit the improvement
upstream, unless upstream no longer exists (I’m not sure if this is the
case here.)
WDYT?
Thanks!
Ludo’.
next prev parent reply other threads:[~2014-02-14 10:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-13 8:00 [PATCH] gnu: xterm: Accept $SHELL even if not in /etc/shells Mark H Weaver
2014-02-13 8:07 ` John Darrington
2014-02-13 8:47 ` Mark H Weaver
2014-02-13 11:06 ` John Darrington
2014-02-13 13:12 ` Ludovic Courtès
2014-02-13 16:29 ` Mark H Weaver
2014-02-14 10:59 ` Ludovic Courtès [this message]
2014-02-14 12:32 ` John Darrington
2014-02-14 13:30 ` Alex Sassmannshausen
2014-02-14 16:59 ` 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=87r4763qp7.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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.