From: Karl Hallsby <karl@hallsby.com>
To: 60661@debbugs.gnu.org
Cc: Karl Hallsby <karl@hallsby.com>
Subject: [bug#60661] [DOCUMENTATION] doc: Example of selecting package output with lisp
Date: Sun, 8 Jan 2023 13:37:55 -0600 [thread overview]
Message-ID: <dea0379eed9180efc4d5afc592caf77bbb26a21a.1673206657.git.karl@hallsby.com> (raw)
* doc/guix.texi (Packages with Multiple Outputs): Give example of how to
select a package's output is a Lisp-y fashion, without using a special
procedure like specification->package.
---
doc/guix.texi | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/doc/guix.texi b/doc/guix.texi
index 293c3016aa..025a73f616 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -4315,6 +4315,23 @@ The command to install its documentation is:
guix install glib:doc
@end example
+While the colon syntax works for command-line specification of package
+outputs, it will not work when specifying the package by Guix name.
+For example, say you want to add only @code{glib}'s documentation to
+your @code{operating-system}'s globally installed packages
+(@pxref{operating-system Reference}).
+
+@lisp
+(use-modules (gnu packages glib))
+;; glib-with-documentation is the Guile symbol for the glib package
+(operating-system
+ ...
+ (packages
+ (append
+ (list (list glib-with-documentation "doc"))
+ %base-packages)))
+@end lisp
+
Some packages install programs with different ``dependency footprints''.
For instance, the WordNet package installs both command-line tools and
graphical user interfaces (GUIs). The former depend solely on the C
base-commit: 812ecf7ee673a3d619d1d3664350508c67e9d92c
--
2.38.1
next reply other threads:[~2023-01-08 19:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-08 19:37 Karl Hallsby [this message]
2023-03-21 20:19 ` bug#60661: [DOCUMENTATION] doc: Example of selecting package output with lisp Maxim Cournoyer
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=dea0379eed9180efc4d5afc592caf77bbb26a21a.1673206657.git.karl@hallsby.com \
--to=karl@hallsby.com \
--cc=60661@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).