From: Charles via Guix-patches via <guix-patches@gnu.org>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: 54375@debbugs.gnu.org
Subject: [bug#54375] Mutable guix shell environments
Date: Mon, 14 Mar 2022 06:24:57 +0000 [thread overview]
Message-ID: <U42QS9XA3iu83SyzCgtOLO_Ody998pm5fmz1JS7nn2tzCjuf8paq5w-Vonz0745nSoRcM7t_kYsL4BEgiERmxl0NxQLIJ33L1k9QliKssgg=@protonmail.com> (raw)
In-Reply-To: <73d3dfc2ceebd68f6afc9af6ae96391933592e07.camel@gmail.com>
> What if instead of just "a package" I wanted to add or remove a package that defines a search path
As with ~/.guix-profile, you will have to . "$GUIX_PROFILE/etc/profile" just like the hint says. For removing, they linger, that is exactly what the default profile does too.
This comes down to us disagreeing which is more important & useful: guix shell semantics vs profile semantics. guix shell --profile could go either way.
Another way to look at it is that I this sequence of 3 commands very useful (so might others). They clearly have something to do with guix profiles, and they spawn a new shell. Thus I thought guix shell --profile was the perfect place for them. You claim they do not belong there. Is there a better place you would suggest?
next prev parent reply other threads:[~2022-03-14 6:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-13 18:21 [bug#54375] Mutable guix shell environments Charles via Guix-patches via
2022-03-13 19:51 ` Liliana Marie Prikler
2022-03-13 23:38 ` Charles via Guix-patches via
2022-03-14 5:19 ` Liliana Marie Prikler
2022-03-14 6:24 ` Charles via Guix-patches via [this message]
2022-03-14 17:43 ` Maxime Devos
2022-03-14 17:54 ` Maxime Devos
2022-03-14 19:41 ` Charles via Guix-patches via
2022-03-14 22:18 ` Ludovic Courtès
2022-03-15 9:49 ` zimoun
2022-03-15 23:52 ` Charles via Guix-patches via
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='U42QS9XA3iu83SyzCgtOLO_Ody998pm5fmz1JS7nn2tzCjuf8paq5w-Vonz0745nSoRcM7t_kYsL4BEgiERmxl0NxQLIJ33L1k9QliKssgg=@protonmail.com' \
--to=guix-patches@gnu.org \
--cc=54375@debbugs.gnu.org \
--cc=charles.b.jackson@protonmail.com \
--cc=liliana.prikler@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).