From: ludo@gnu.org (Ludovic Courtès)
To: 宋文武 <iyzsong@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: /etc/profile and .zshrc skeleton
Date: Sun, 07 Dec 2014 21:35:48 +0100 [thread overview]
Message-ID: <87sigrmc4b.fsf@gnu.org> (raw)
In-Reply-To: <87sigs85nq.fsf@gmail.com> ("宋文武"'s message of "Sun, 07 Dec 2014 12:06:49 +0800")
宋文武 <iyzsong@gmail.com> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>> One last thing: I think CPATH and LIBRARY_PATH (and eventually
>> additional search path variables) should remain in /etc/profile.
> I'll prefer use `guix environment' for dev, just install applications to
> profile.
I agree that ‘guix environment’ is usually the preferred approach.
Yet, I thought it may be better to keep the other approach working out
of the box by default, to avoid unnecessary user frustration.
Thinking more, there are a number of other search path environment
variables that would be candidate for /etc/profile: GUILE_LOAD_PATH,
PKG_CONFIG_PATH, MANPATH, PERL5LIB, etc. But perhaps some of them are
better left handled by the user? How would we draw the line between
those that /etc/profile defines by default, and those that users have to
define by themselves?
Thanks,
Ludo’.
prev parent reply other threads:[~2014-12-07 20:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 15:58 use zsh as login shell 宋文武
2014-11-27 20:15 ` Ludovic Courtès
2014-11-28 15:06 ` 宋文武
2014-11-28 22:26 ` Ludovic Courtès
2014-11-29 3:24 ` 宋文武
2014-12-01 12:57 ` Ludovic Courtès
2014-12-02 14:43 ` 宋文武
2014-12-04 23:10 ` Ludovic Courtès
2014-12-05 5:11 ` Mark H Weaver
2014-12-05 18:54 ` Ludovic Courtès
2014-12-05 11:21 ` 宋文武
2014-12-06 8:04 ` use zsh and fish " 宋文武
2014-12-06 15:09 ` Ludovic Courtès
2014-11-28 15:11 ` use zsh " 宋文武
2014-12-05 13:57 ` 宋文武
2014-12-06 22:35 ` /etc/profile and .zshrc skeleton Ludovic Courtès
2014-12-07 4:06 ` 宋文武
2014-12-07 20:35 ` 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
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=87sigrmc4b.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=iyzsong@gmail.com \
/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).