From: EuAndreh via Guix-patches via <guix-patches@gnu.org>
To: 58874@debbugs.gnu.org
Cc: EuAndreh <eu@euandre.org>
Subject: [bug#58874] [PATCH] doc: Update reference to special-files-service-type.
Date: Fri, 28 Oct 2022 23:40:09 -0300 [thread overview]
Message-ID: <20221029024009.10930-1-eu@euandre.org> (raw)
* doc/guix.texi (Base Services): Update what the default value of
special-files-service-type is, which already includes /usr/bin/env,
and the accompanying examples.
---
The code for special-files-service-type changed in
a9162155975a131afa1e6a44262afbb7af91f7fd, this is the equivalent
documentation change.
doc/guix.texi | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/doc/guix.texi b/doc/guix.texi
index 80fb3bc47f..449049fcc8 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -17711,17 +17711,19 @@ and the second element is its target. By default it is:
@cindex @file{/bin/sh}
@cindex @file{sh}, in @file{/bin}
@lisp
-`(("/bin/sh" ,(file-append bash "/bin/sh")))
+`(("/bin/sh" ,(file-append bash "/bin/sh"))
+ ("/usr/bin/env" ,(file-append coreutils "/bin/env")))
@end lisp
@cindex @file{/usr/bin/env}
@cindex @file{env}, in @file{/usr/bin}
-If you want to add, say, @code{/usr/bin/env} to your system, you can
+If you want to add, say, @code{/bin/bash} to your system, you can
change it to:
@lisp
`(("/bin/sh" ,(file-append bash "/bin/sh"))
- ("/usr/bin/env" ,(file-append coreutils "/bin/env")))
+ ("/usr/bin/env" ,(file-append coreutils "/bin/env"))
+ ("/bin/bash" ,(file-append bash "/bin/bash")))
@end lisp
Since this is part of @code{%base-services}, you can use
--
2.38.0
next reply other threads:[~2022-10-29 19:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-29 2:40 EuAndreh via Guix-patches via [this message]
2022-11-03 16:42 ` bug#58874: [PATCH] doc: Update reference to special-files-service-type Christopher Baines
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=20221029024009.10930-1-eu@euandre.org \
--to=guix-patches@gnu.org \
--cc=58874@debbugs.gnu.org \
--cc=eu@euandre.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).