From: Ricardo Wurmus <rekado@elephly.net>
To: Philip McGrath <philip@philipmcgrath.com>
Cc: Peter Polidoro <peter@polidoro.io>,
Julien Lepiller <julien@lepiller.eu>,
help-guix@gnu.org
Subject: Re: Finding Dependencies at Run Time
Date: Thu, 14 Jul 2022 13:28:27 +0200 [thread overview]
Message-ID: <87a69cvsh7.fsf@elephly.net> (raw)
In-Reply-To: <272df5fb-1239-46a5-a6df-82cee96fd3ac@www.fastmail.com>
"Philip McGrath" <philip@philipmcgrath.com> writes:
> On Thu, Jul 14, 2022, at 4:25 AM, Ricardo Wurmus wrote:
>> Peter Polidoro <peter@polidoro.io> writes:
>>
>>> Your explanations are very helpful, thank you, and your links made me
>>> realize that devel version of the manual has lots of information that
>>> I could not find in the stable version of the manual.
>>
>> We recommend using the manual that comes with Guix, because it matches
>> the particular version of Guix you have installed. You can use any Info
>> reader to view the manual and the cookbook.
>>
>
> I mentioned this somewhere before, but I would love to be able to install a local copy of the HTML manual with the nice styling used on the website.
You can build all HTML and PDF versions of the manual with
./pre-inst-env guix build -f doc/build.scm
from a Guix checkout. This will take a little while.
The convenience of using the Info document is that it is installed with
“guix pull”, so it will always match your current version of Guix. The
Info document is also more accessible than the HTML version because of
the manually curated index (hit “i” in your Info reader and type away to
get to a topic more quickly).
--
Ricardo
next prev parent reply other threads:[~2022-07-14 11:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 14:56 Finding Dependencies at Run Time Peter Polidoro
2022-07-13 16:03 ` Julien Lepiller
2022-07-13 17:47 ` Peter Polidoro
2022-07-13 18:39 ` Julien Lepiller
2022-07-13 18:51 ` Peter Polidoro
2022-07-13 21:02 ` Julien Lepiller
2022-07-14 17:47 ` Peter Polidoro
2022-07-16 21:53 ` Thiago Jung Bauermann
2022-07-14 8:25 ` Ricardo Wurmus
2022-07-14 8:48 ` Philip McGrath
2022-07-14 11:28 ` Ricardo Wurmus [this message]
2022-07-14 13:27 ` zimoun
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=87a69cvsh7.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=help-guix@gnu.org \
--cc=julien@lepiller.eu \
--cc=peter@polidoro.io \
--cc=philip@philipmcgrath.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).