From: ludo@gnu.org (Ludovic Courtès)
To: Alex Kost <alezost@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] doc: Clarify and consolidate modify-services documentation.
Date: Fri, 18 Mar 2016 22:11:33 +0100 [thread overview]
Message-ID: <87bn6bjxtm.fsf@gnu.org> (raw)
In-Reply-To: <87egb8z0zb.fsf@gmail.com> (Alex Kost's message of "Fri, 18 Mar 2016 10:42:00 +0300")
Alex Kost <alezost@gmail.com> skribis:
> Ludovic Courtès (2016-03-17 11:52 +0300) wrote:
>
>> Alex Kost <alezost@gmail.com> skribis:
>>
>>> Chris Marusich (2016-03-12 14:38 +0300) wrote:
>>>
>>>> From bf03c0a3fa35144342849cdf550219a185fbf10d Mon Sep 17 00:00:00 2001
>>>> From: Chris Marusich <cmmarusich@gmail.com>
>>>> Date: Mon, 7 Mar 2016 01:55:07 -0800
>>>> Subject: [PATCH] doc: Clarify and consolidate modify-services documentation.
>>>>
>>>> * doc/guix.texi ("Using the Configuration System": Move the example...
>>>> * doc/guix.texi ("Service Reference"): ...to here, and clarify more.
>>>> * gnu/services.scm (modify-services): Update docstring to match.
>>>
>>> [...]
>>>> -This is a shorthand for:
>>>> +The @var{body} should evaluate to the new service parameters, which will
>>>> +be used to configure the new service. This new service will replace the
>>>> +original in the resulting list. Because a service's service parameters
>>>> +are created using @code{define-record-type*}, you can write a succint
>>>> +@var{body} that evaluates to the new service parameters by using the
>>>> +@code{inherit} feature that @code{define-record-type*} provides.
>>>> +
>>>> +@xref{Using the Configuration System} for example usage.
>>>
>>> Now there is a compilation warning, as makeinfo doesn't like this line:
>>>
>>> ./doc/guix.texi:10138: warning: `.' or `,' must follow @xref
>>
>> Pushed the obvious fix, thanks.
>>
>> I guess most of us are using Texinfo 6.1 now and won’t notice.
>
> Oh, I've never noticed that I use 6.0. It's because I update my
> profiles using "guix package --manifest" facility and:
>
> (@ (gnu packages texinfo) texinfo) gives Texinfo 6.0
>
> Is there a reason why we keep so many versions of texinfo? In
> particular why there is ‘texinfo-6.1’ variable, while ‘texinfo’ is still
> 6.0?
It’s just that the upgrade wuold trigger a full rebuild.
We should replace 6.0 with 6.1 in ‘core-updates’. Would you like to
take care of it?
(4.3 is kept in the installer because it has a smaller footprint.)
Ludo’.
next prev parent reply other threads:[~2016-03-18 21:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 10:58 [PATCH] doc: Clarify and consolidate modify-services documentation Chris Marusich
2016-03-11 14:15 ` Ludovic Courtès
2016-03-12 11:30 ` Chris Marusich
2016-03-12 11:38 ` Chris Marusich
2016-03-13 7:33 ` Chris Marusich
2016-03-15 14:56 ` Ludovic Courtès
2016-03-17 8:12 ` Alex Kost
2016-03-17 8:52 ` Ludovic Courtès
2016-03-18 7:42 ` Alex Kost
2016-03-18 21:11 ` Ludovic Courtès [this message]
2016-03-19 8:46 ` [PATCH] gnu: texinfo: Use version 6.1 by default Alex Kost
2016-03-19 21:02 ` Ludovic Courtès
2016-03-23 8:41 ` Alex Kost
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=87bn6bjxtm.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=alezost@gmail.com \
--cc=guix-devel@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).