From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Zelphir Kaltstahl <zelphirkaltstahl@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: define PATH and PROFILE
Date: Mon, 04 Jan 2021 18:56:42 +0100 [thread overview]
Message-ID: <87ft3gfuw5.fsf@nckx> (raw)
In-Reply-To: <a3584c32-3164-3432-513a-45f89cb4ad6b@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 908 bytes --]
Hi Zelphir, Christophe,
Zelphir Kaltstahl 写道：
> Some time ago I created this:
> https://notabug.org/ZelphirKaltstahl/guix-package-manager-tutorials/src/33f519f2517685106b71399993a7da94cad84d3b/dot-profile-file.org
Thanks for sharing!
Not directly related, but I just want to point out that you
shouldn't ‘need’ any of it just to make Guix go.
Editing ~/.profile isn't a routine thing on a routine Guix
installation, although for some reason some people believe
otherwise. I'm not sure why. Adding magic incantations to it can
cause hard-to-diagnose bugs, even long after the fact. 's Why it
triggers me so; forgive me :-)
If Guix or its packages don't work without them, and you're not
customising things like Zelphir, please pop in and tell us. Only
add things to ~/.profile that are somehow ‘personal’, and that you
understand.
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2021-01-04 17:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.103.1609779610.25319.help-guix@gnu.org>
2021-01-04 17:07 ` define PATH and PROFILE Zelphir Kaltstahl
2021-01-04 17:56 ` Tobias Geerinckx-Rice [this message]
2021-01-04 21:19 ` Zelphir Kaltstahl
2021-01-03 18:59 Christophe Pisteur
2021-01-03 20:49 ` Tobias Geerinckx-Rice
2021-01-03 22:01 ` Christophe Pisteur
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=87ft3gfuw5.fsf@nckx \
--to=me@tobias.gr \
--cc=help-guix@gnu.org \
--cc=zelphirkaltstahl@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.
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).