bug#26733: document (list package output) in operating-system-packages

bug#26733: document (list package output) in operating-system-packages

[Julien Lepiller]

[-- Attachment #1: Type: text/plain, Size: 99 bytes --]

Hi,

here is a small patch to document how to make globally visible a
specific output of a package.

[-- Attachment #2: 0001-doc-Document-list-package-output-syntax-in-operantin.patch --]
[-- Type: text/x-patch, Size: 1349 bytes --]

From 6a71d7613bbabdde9d43de5ff09601195f9f49ee Mon Sep 17 00:00:00 2001
From: Julien Lepiller <julien@lepiller.eu>
Date: Mon, 1 May 2017 15:44:31 +0200
Subject: [PATCH] doc: Document (list package output) syntax in
 operanting-system-packages.

* doc/guix.texi (Globally-Visible Packages): Document (PACKAGE OUTPUT) syntax.
---
 doc/guix.texi | 14 +++++++++++++-
 1 file changed, 13 insertions(+), 1 deletion(-)

diff --git a/doc/guix.texi b/doc/guix.texi
index 957ce2bab..3ae9a1cd5 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -7678,7 +7678,19 @@ provides all the tools one would expect for basic user and administrator
 tasks---including the GNU Core Utilities, the GNU Networking Utilities,
 the GNU Zile lightweight text editor, @command{find}, @command{grep},
 etc.  The example above adds tcpdump to those, taken from the @code{(gnu
-packages admin)} module (@pxref{Package Modules}).
+packages admin)} module (@pxref{Package Modules}).  The
+@code{(list package output)} syntax can be used to add a specific output
+of a package:
+
+@lisp
+(use-modules (gnu packages))
+(use-modules (gnu packages dns))
+
+(operating-system
+  ;; ...
+  (packages (cons (list bind "utils")
+                  %base-packages)))
+@end lisp
 
 @findex specification->package
 Referring to packages by variable name, like @var{tcpdump} above, has
-- 
2.12.2

bug#26733: document (list package output) in operating-system-packages

[Kei Kebreau]

[-- Attachment #1: Type: text/plain, Size: 1743 bytes --]

Julien Lepiller <julien@lepiller.eu> writes:

> Hi,
>
> here is a small patch to document how to make globally visible a
> specific output of a package.
>
>>From 6a71d7613bbabdde9d43de5ff09601195f9f49ee Mon Sep 17 00:00:00 2001
> From: Julien Lepiller <julien@lepiller.eu>
> Date: Mon, 1 May 2017 15:44:31 +0200
> Subject: [PATCH] doc: Document (list package output) syntax in
>  operanting-system-packages.
>
> * doc/guix.texi (Globally-Visible Packages): Document (PACKAGE OUTPUT) syntax.
> ---
>  doc/guix.texi | 14 +++++++++++++-
>  1 file changed, 13 insertions(+), 1 deletion(-)
>
> diff --git a/doc/guix.texi b/doc/guix.texi
> index 957ce2bab..3ae9a1cd5 100644
> --- a/doc/guix.texi
> +++ b/doc/guix.texi
> @@ -7678,7 +7678,19 @@ provides all the tools one would expect for basic user and administrator
>  tasks---including the GNU Core Utilities, the GNU Networking Utilities,
>  the GNU Zile lightweight text editor, @command{find}, @command{grep},
>  etc.  The example above adds tcpdump to those, taken from the @code{(gnu
> -packages admin)} module (@pxref{Package Modules}).
> +packages admin)} module (@pxref{Package Modules}).  The
> +@code{(list package output)} syntax can be used to add a specific output
> +of a package:
> +
> +@lisp
> +(use-modules (gnu packages))
> +(use-modules (gnu packages dns))
> +
> +(operating-system
> +  ;; ...
> +  (packages (cons (list bind "utils")
> +                  %base-packages)))
> +@end lisp
>  
>  @findex specification->package
>  Referring to packages by variable name, like @var{tcpdump} above, has

At first glance this change looks okay, but I'll wait for a second
opinion to be safe (I don't usually review documentation changes).

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

bug#26733: document (list package output) in operating-system-packages

[Ludovic Courtès]

Kei Kebreau <kei@openmailbox.org> skribis:

> Julien Lepiller <julien@lepiller.eu> writes:
>
>> Hi,
>>
>> here is a small patch to document how to make globally visible a
>> specific output of a package.
>>
>>>From 6a71d7613bbabdde9d43de5ff09601195f9f49ee Mon Sep 17 00:00:00 2001
>> From: Julien Lepiller <julien@lepiller.eu>
>> Date: Mon, 1 May 2017 15:44:31 +0200
>> Subject: [PATCH] doc: Document (list package output) syntax in
>>  operanting-system-packages.
>>
>> * doc/guix.texi (Globally-Visible Packages): Document (PACKAGE OUTPUT) syntax.
>> ---
>>  doc/guix.texi | 14 +++++++++++++-
>>  1 file changed, 13 insertions(+), 1 deletion(-)
>>
>> diff --git a/doc/guix.texi b/doc/guix.texi
>> index 957ce2bab..3ae9a1cd5 100644
>> --- a/doc/guix.texi
>> +++ b/doc/guix.texi
>> @@ -7678,7 +7678,19 @@ provides all the tools one would expect for basic user and administrator
>>  tasks---including the GNU Core Utilities, the GNU Networking Utilities,
>>  the GNU Zile lightweight text editor, @command{find}, @command{grep},
>>  etc.  The example above adds tcpdump to those, taken from the @code{(gnu
>> -packages admin)} module (@pxref{Package Modules}).
>> +packages admin)} module (@pxref{Package Modules}).  The
>> +@code{(list package output)} syntax can be used to add a specific output
>> +of a package:
>> +
>> +@lisp
>> +(use-modules (gnu packages))
>> +(use-modules (gnu packages dns))
>> +
>> +(operating-system
>> +  ;; ...
>> +  (packages (cons (list bind "utils")
>> +                  %base-packages)))
>> +@end lisp
>>  
>>  @findex specification->package
>>  Referring to packages by variable name, like @var{tcpdump} above, has
>
> At first glance this change looks okay, but I'll wait for a second
> opinion to be safe (I don't usually review documentation changes).

LGTM too.

Thanks,
Ludo’.

bug#26733: (no subject)

[Julien Lepiller]