From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix Devel <guix-devel@gnu.org>, Amin Bandali <bandali@gnu.org>
Subject: Re: Web site moved to https://guix.gnu.org
Date: Thu, 18 Jul 2019 14:39:45 +0200 [thread overview]
Message-ID: <CAJ3okZ3CtiStkLcjgM_X8QBX0xnNzSJo9iG+usDKDcXQ_81xqQ@mail.gmail.com> (raw)
In-Reply-To: <87ef2o72xc.fsf@gnu.org>
Dear,
Thank you for the work of this move! :-)
On Wed, 17 Jul 2019 at 23:43, Ludovic Courtès <ludo@gnu.org> wrote:
> As discussed in <https://issues.guix.gnu.org/issue/36708>, that should
> allow us to dynamically serve or to periodically update the package
> list. Help welcome!
>
> For now, an advantage of the new setup is that everything that’s
> published is automatically updated and built from source (using Haunt
> for the web site and ‘doc/build.scm’ in Guix for the manual). You can
> see the whole config at:
Because not everyone reads the documentation with `info`, it appears
to me nice to also serve the latest version of the manual (at least
periodically build from source).
The page [1] says 1.0.1 — 16 July 2019 which follows the branch
`version-1.0.1` ; I guess.
It should be interesting to be able to read online the documentation
of the branch `master` which is followed by default by `guix pull`. So
what do you think to add a section to [1] for `master` documentation
say built nightly?
Closely related and I think it has already been discussed (but I do
not find the last words or the blocking points), is it possible to
output the documentation in HTML too?
All the best,
simon
[1] https://guix.gnu.org/manual/en/
next prev parent reply other threads:[~2019-07-18 12:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-17 21:43 Web site moved to https://guix.gnu.org Ludovic Courtès
2019-07-18 12:39 ` zimoun [this message]
2019-07-18 12:44 ` Julien Lepiller
2019-07-18 15:17 ` zimoun
2019-07-18 15:27 ` zimoun
2019-07-24 17:13 ` Ludovic Courtès
2019-07-19 6:18 ` Chris Marusich
2019-07-19 15:13 ` N
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=CAJ3okZ3CtiStkLcjgM_X8QBX0xnNzSJo9iG+usDKDcXQ_81xqQ@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=bandali@gnu.org \
--cc=guix-devel@gnu.org \
--cc=ludo@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).