GNU bug report logs - #26733
document (list package output) in operating-system-packages

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 26733 in the body.
You can then email your comments to 26733 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Julien Lepiller <julien <at> lepiller.eu>
To: guix-patches <at> gnu.org
Subject: document (list package output) in operating-system-packages
Date: Mon, 1 May 2017 15:51:55 +0200

[Message part 1 (text/plain, inline)]

Hi,

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

[0001-doc-Document-list-package-output-syntax-in-operantin.patch (text/x-patch, attachment)]

Message #8 received at 26733 <at> debbugs.gnu.org (full text, mbox):

From: Kei Kebreau <kei <at> openmailbox.org>
To: Julien Lepiller <julien <at> lepiller.eu>
Cc: 26733 <at> debbugs.gnu.org
Subject: Re: bug#26733: document (list package output) in
 operating-system-packages
Date: Thu, 04 May 2017 15:07:18 -0400

[Message part 1 (text/plain, inline)]

Julien Lepiller <julien <at> 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 <at> 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).

[signature.asc (application/pgp-signature, inline)]

Message #11 received at 26733 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: Kei Kebreau <kei <at> openmailbox.org>
Cc: Julien Lepiller <julien <at> lepiller.eu>, 26733 <at> debbugs.gnu.org
Subject: Re: bug#26733: document (list package output) in
 operating-system-packages
Date: Fri, 05 May 2017 09:55:04 +0200

Kei Kebreau <kei <at> openmailbox.org> skribis:

> Julien Lepiller <julien <at> 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 <at> 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’.

Message #16 received at 26733-done <at> debbugs.gnu.org (full text, mbox):

From: Julien Lepiller <julien <at> lepiller.eu>
To: 26733-done <at> debbugs.gnu.org
Date: Sat, 6 May 2017 10:03:38 +0200

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.