all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
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:21:19 +0100	[thread overview]
Message-ID: <87fsevw25s.fsf@gnu.org> (raw)
In-Reply-To: <86wn87lxwv.fsf@gmail.com> (zimoun's message of "Sun, 06 Nov 2022 19:50:56 +0100")

Hi,

zimoun <zimon.toutoune@gmail.com> skribis:

> On Sat, 05 Nov 2022 at 19:03, Ludovic Courtès <ludo@gnu.org> wrote:

[...]

>> Nice!  Including channel info in the document like you do here is
>> probably a major use case; it also makes a lot of sense in the context
>> of reproducible research workflows.
>
> Ludo, what do you have in mind about reproducible research workflow?

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.

Ludo’.


  parent reply	other threads:[~2022-11-07  9:22 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 [this message]
2022-11-07  9:47             ` zimoun
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fsevw25s.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=phil@beadling.co.uk \
    --cc=zimon.toutoune@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. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.