From: ludo@gnu.org (Ludovic Courtès)
To: Craig Barnes <cjbarnes18@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Should we start a Guix users wiki?
Date: Thu, 10 Sep 2015 15:58:57 +0200 [thread overview]
Message-ID: <877fny4bq6.fsf@gnu.org> (raw)
In-Reply-To: <55F15FB8.1010000@gmail.com> (Craig Barnes's message of "Thu, 10 Sep 2015 11:47:20 +0100")
Craig Barnes <cjbarnes18@gmail.com> skribis:
> On 08/09/15 15:37, Mark H Weaver wrote:
>> ludo@gnu.org (Ludovic Courtès) writes:
[...]
>>> I have mixed feelings. There are several issues with a Wiki: one can
>>> hardly know which version of the software it’s talking about (whereas
>>> the installed Info pages of PDFs necessarily match the installed
>>> version), and more importantly, it tends to be disorganized,
>>> unmaintained, and often misleading.
> In order to make sure that examples in the manual aren't broken,
> wouldn't something equivalent to python doctests be necessary to ensure
> this? I think it would be worse to have a broken example in the manual
> than somewhere else. If the number of examples grow this could be
> equally unmaintainable.
Good point. Examples that were added lately have been put in separate
files so that we can at least manually test that they work as
advertised.
Now, I think it would be good to add targets in ‘doc.am’ to
automatically check the examples. I think these wouldn’t be in-depth
tests. For example, for OS declarations, we could simply make sure that
‘guix system build EXAMPLE --dry-run’ passes. Likewise for the ‘guix
environment --load’ example.
WDYT?
I could add a couple of rules in ‘doc.am’ so that people have a template
to reuse when they add new examples.
(I do think we need VM- or container-based tests of complete systems,
but that’s a separate issue IMO.)
> Going back to my original problem of finding information that isn't
> currently in the manual, it would be great if there where an easier way
> to search / browse the mailing list archives. This would make
> extracting great examples to add to the manual easier. Any suggestions
> would be appreciated.
There’s a search facility at
<https://lists.gnu.org/archive/cgi-bin/namazu.cgi?idxname=guix-devel>
that is not perfect, but a good start.
Alternately there’s the GMane mirror at
<http://dir.gmane.org/gmane.comp.gnu.guix.devel>, which supports both
searching and browsing.
The email client that I use, Gnus, also provides handy search facility
and the ability to browse the complete history of a GMane group over
NNTP.
HTH,
Ludo’.
next prev parent reply other threads:[~2015-09-10 13:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-07 22:08 Should we start a Guix users wiki? Craig Barnes
2015-09-08 8:01 ` Amirouche Boubekki
2015-09-08 9:54 ` Ludovic Courtès
2015-09-08 12:40 ` Thompson, David
2015-09-08 14:37 ` Mark H Weaver
2015-09-10 10:47 ` Craig Barnes
2015-09-10 13:58 ` Ludovic Courtès [this message]
2015-09-10 15:35 ` Cook, Malcolm
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=877fny4bq6.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=cjbarnes18@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).