From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Proposal for a blog contribution on reproducible computations
Date: Sat, 11 Jan 2020 10:39:36 +0100 [thread overview]
Message-ID: <m18smebacn.fsf@ordinateur-de-catherine--konrad.home> (raw)
In-Reply-To: <878smfutv8.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> Another thing that comes to mind: would it make sense to mention ‘guix
> graph’ in the part where you pipe the output of ‘guix show’ to ‘recsel’,
> etc.?
Forgot that one, sorry. Yes, it would make sense, though I'd place it a
bit later in the text. But I'd have to figure out first how how the
various options of "guix graph" relate exactly to what I am writing.
‘package’
This is the default type used in the example above. It shows the
DAG of package objects, excluding implicit dependencies. It is
concise, but filters out many details.
Are "implicit dependencies" those added by the build system? If yes,
this edges in this graph would correspond to package-direct-inputs.
‘bag’
Similar to ‘bag-emerged’, but this time including all the bootstrap
dependencies.
And that is package-closure with arrows defined by bag-direct-inputs, right?
Cheers,
Konrad.
next prev parent reply other threads:[~2020-01-11 9:39 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 14:16 Feedback from JRES in Dijon Julien Lepiller
2019-12-05 14:34 ` Pierre Neidhardt
2019-12-05 14:42 ` Julien Lepiller
2019-12-05 15:44 ` Konrad Hinsen
2019-12-05 15:52 ` zimoun
2019-12-06 7:07 ` Bengt Richter
2019-12-06 12:24 ` Konrad Hinsen
2019-12-07 16:35 ` Timothy Sample
2019-12-08 2:48 ` Bengt Richter
2019-12-08 4:11 ` Timothy Sample
2019-12-08 23:09 ` Bengt Richter
2019-12-09 5:23 ` Konrad Hinsen
2019-12-06 12:57 ` Konrad Hinsen
2019-12-10 16:57 ` Ludovic Courtès
2019-12-11 20:48 ` Konrad Hinsen
2020-01-07 16:05 ` Proposal for a blog contribution on reproducible computations Konrad Hinsen
2020-01-09 20:40 ` zimoun
2020-01-10 16:59 ` Ludovic Courtès
2020-01-10 17:19 ` zimoun
2020-01-10 18:53 ` Giovanni Biscuolo
2020-01-11 9:31 ` Konrad Hinsen
2020-01-11 14:05 ` Giovanni Biscuolo
2020-01-13 8:37 ` Ludovic Courtès
2020-01-14 9:06 ` Konrad Hinsen
2020-01-14 15:38 ` Ludovic Courtès
2020-01-14 16:18 ` Konrad Hinsen
2020-01-14 16:40 ` Ludovic Courtès
2020-01-10 17:03 ` Ludovic Courtès
2020-01-11 9:39 ` Konrad Hinsen [this message]
2020-01-15 22:20 ` Ludovic Courtès
2019-12-05 15:47 ` Feedback from JRES in Dijon zimoun
2019-12-05 14:39 ` Julien Lepiller
2019-12-05 15:42 ` zimoun
2019-12-10 17:06 ` 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=m18smebacn.fsf@ordinateur-de-catherine--konrad.home \
--to=konrad.hinsen@fastmail.net \
--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 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.