From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Phil <phil@beadling.co.uk>, guix-devel@gnu.org
Subject: Re: Compile skribilo doc containing guix channel references
Date: Mon, 07 Nov 2022 10:47:54 +0100 [thread overview]
Message-ID: <875yfr9jud.fsf@gmail.com> (raw)
In-Reply-To: <87fsevw25s.fsf@gnu.org>
Hi Ludo,
On lun., 07 nov. 2022 at 10:21, Ludovic Courtès <ludo@gnu.org> wrote:
> In a published paper, it’d be useful to include channel information, and
> Skribilo/Guix integration is one way to do that. For the convenience of
> people who do not use Guix, some might also find it to include
> approximate package metadata such as name/version pairs, as in that 2015
> paper.
About the channel information to include in a published paper, yeah
Skribilo/Guix is one (non-straightforwardly?) way to get “guix describe
-f channels”. ;-)
Is it possible to have a Skribilo reader which would use less
parenthesis? Similar to Racket Scribble?
Well, if I understand correctly, «the context of reproducible research
workflows» somehow means using Skribilo as authoring system for
producing “active papers“, right?
Cheers,
simon
PS: About the name/version pairs, are we not trying to explain at length
that it is the wrong way to obtain reproducibility? Aside it is not
clear what is the depth of name/version pairs to provide when speaking
about reproducibility, no?
next prev parent reply other threads:[~2022-11-07 9:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-30 20:46 Compile skribilo doc containing guix channel references Phil
2022-10-31 21:56 ` Phil
2022-11-02 11:36 ` Ludovic Courtès
2022-11-04 22:13 ` Phil
2022-11-05 16:40 ` Phil
2022-11-05 18:03 ` Ludovic Courtès
2022-11-06 18:50 ` zimoun
2022-11-06 22:12 ` Phil
2022-11-07 8:37 ` zimoun
2022-11-07 9:21 ` Ludovic Courtès
2022-11-07 9:47 ` zimoun [this message]
2022-11-10 11:58 ` Ludovic Courtès
2022-11-10 12:39 ` zimoun
2022-11-17 14:54 ` Ludovic Courtès
2022-11-05 17:58 ` Ludovic Courtès
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=875yfr9jud.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=phil@beadling.co.uk \
/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).