From: Lee Fallat <inbox@leefallat.ca>
To: 46477@debbugs.gnu.org
Subject: [bug#46477] [patch] Explain how to exit and clean up a guix environment
Date: Fri, 12 Feb 2021 19:35:04 -0500 [thread overview]
Message-ID: <5db18d83a7864aca2c00db3cc5683758fbbafe72.camel@leefallat.ca> (raw)
[-- Attachment #1: Type: text/plain, Size: 208 bytes --]
I accidentally sent the patch to the wrong mailing list and was pointed
to this one (thanks Tobias!).
I've attached the patch to this email as well (this time using git
format-patch instead of git diff -u).
[-- Attachment #2: 0001-Explain-how-to-exit-and-clean-up-a-guix-environment.patch --]
[-- Type: text/x-patch, Size: 1135 bytes --]
From 607c3af436c80744acf8a878c19e191d82f6cdda Mon Sep 17 00:00:00 2001
From: Lee <inbox@leefallat.ca>
Date: Fri, 12 Feb 2021 16:44:56 -0500
Subject: [PATCH] Explain how to exit and clean up a guix environment
The current documentation doesn't explain how to exit an environment or how to
remove the packages after exiting.
---
doc/guix.texi | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/doc/guix.texi b/doc/guix.texi
index 68abb968b0..e7c55e00da 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -5558,6 +5558,10 @@ they should be defined in @file{.bash_profile}, which is sourced only by
log-in shells. @xref{Bash Startup Files,,, bash, The GNU Bash Reference
Manual}, for details on Bash start-up files.}.
+Exiting from a guix environment is the same as exiting from the shell, and will
+place the user back in the old enviroment before @command{guix enviroment} was
+invoked. To clean up packages which were installed invoke @command{guix gc}.
+
@vindex GUIX_ENVIRONMENT
@command{guix environment} defines the @env{GUIX_ENVIRONMENT}
variable in the shell it spawns; its value is the file name of the
--
2.30.0
next reply other threads:[~2021-02-13 1:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-13 0:35 Lee Fallat [this message]
2021-02-15 11:08 ` bug#46477: [patch] Explain how to exit and clean up a guix environment Nicolas Goaziou
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=5db18d83a7864aca2c00db3cc5683758fbbafe72.camel@leefallat.ca \
--to=inbox@leefallat.ca \
--cc=46477@debbugs.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 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).