From: Leo Famulari <leo@famulari.name>
To: Vincent Legoll <vincent.legoll@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Documentation
Date: Fri, 2 Sep 2016 12:08:34 -0400 [thread overview]
Message-ID: <20160902160834.GA24996@jasmine> (raw)
In-Reply-To: <CAEwRq=rMnT55mFVXEbvsgFGobmXd+ij5RWdXJ2ODzNmvqfDT2w@mail.gmail.com>
On Fri, Sep 02, 2016 at 05:45:02PM +0200, Vincent Legoll wrote:
> when & how is the documentation here :
> https://www.gnu.org/software/guix/manual/guix.html
> updated ?
I'm not sure, but I think it's updated whenever we make a new release.
> Then I searched how to build the doc, and found in README:
>
> See the manual for the installation instructions, either by running
>
> info -f doc/guix.info "(guix) Installation"
>
> but...
>
> info: doc/guix.info: No such file or directory
On GuixSD, `info guix` should work. On other systems...
> So how do I make that doc so that I can read the "installation
> instructions" which will tell me how to make the doc...
... from a checkout of our Git repo, you can do:
`guix environment guix -- make doc/guix.info`
Similarly, you can do `make doc/guix.html`.
If the Git checkout is new, you will need to run the ./configure script
first. And if so, you almost always want to do it like this:
`./configure --localstatedir=/var`.
https://www.gnu.org/software/guix/manual/html_node/Building-from-Git.html#Building-from-Git
next prev parent reply other threads:[~2016-09-02 16:09 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 ` Leo Famulari [this message]
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 ` Documentation Ludovic Courtès
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=20160902160834.GA24996@jasmine \
--to=leo@famulari.name \
--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).