From: ludo@gnu.org (Ludovic Courtès)
To: Vincent Legoll <vincent.legoll@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Documentation
Date: Sat, 03 Sep 2016 12:43:48 +0200 [thread overview]
Message-ID: <87twdxntzv.fsf@gnu.org> (raw)
In-Reply-To: <CAEwRq=q1n0RrpEHfOwgADg1fZ3oFTkvxJC6V71fVDL8vBrKPsA@mail.gmail.com> (Vincent Legoll's message of "Fri, 2 Sep 2016 19:46:51 +0200")
Vincent Legoll <vincent.legoll@gmail.com> skribis:
>>> Or maybe I'm very bad at info, always found its interface weird...
>>
>> I'm not sure, I actually don't use `info` very much either. Maybe your
>> GuixSD installation has not been updated since the relevant text was
>> added to the manual?
>
> I regularly do guix pull && guix system reconfigure, like earlier today...
>
> Isn't that enough ?
>
> Which package contains this documentation ?
It contains the documentation of the currently-packaged Guix snapshot:
--8<---------------cut here---------------start------------->8---
$ guix package -A guix
guix 0.11.0 out gnu/packages/package-management.scm:71:2
guix 0.11.0-1.4420 out gnu/packages/package-management.scm:216:4
--8<---------------cut here---------------end--------------->8---
We update the snapshot once every few weeks.
Eventually ‘guix pull’ will be able to update guix.info; it doesn’t do
that currently, which is a problem as you noticed.
>>> $ ./configure --localstatedir=/var
>>> configure: error: cannot find install-sh, install.sh, or shtool in
>>> build-aux "."/build-aux
>>
>> Sorry, I forgot the first step, `./bootstrap`, which is mentioned here:
>
> OK, after ./bootstrap, now ./configure --localstatedir=/var works, but not:
>
> $ make doc/guix.html
Try “make && make html”.
However, I think you should try ‘info’ again. The interface is not any
weirder than that of a browser after all, see “info info”. :-)
Ludo’.
next prev parent reply other threads:[~2016-09-03 10:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-02 15:45 Documentation Vincent Legoll
2016-09-02 16:08 ` Documentation Leo Famulari
2016-09-02 16:45 ` Documentation Vincent Legoll
2016-09-02 17:09 ` Documentation Leo Famulari
2016-09-02 17:46 ` Documentation Vincent Legoll
2016-09-02 18:45 ` Documentation Leo Famulari
2016-09-03 10:43 ` Ludovic Courtès [this message]
2016-09-02 22:43 ` Documentation myglc2
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=87twdxntzv.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=help-guix@gnu.org \
--cc=vincent.legoll@gmail.com \
/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.
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).