From: jgart <jgart@dismail.de>
To: Julien Lepiller <julien@lepiller.eu>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: guix graph build phases
Date: Mon, 5 Dec 2022 10:10:43 -0600 [thread overview]
Message-ID: <20221205101043.GC26516@dismail.de> (raw)
In-Reply-To: <FE3007F1-C201-4C92-A04D-7AA03FE1F271@lepiller.eu>
On Tue, 22 Nov 2022 23:12:16 +0100 Julien Lepiller <julien@lepiller.eu> wrote:
> The graph will always be flat, since it's a list, so graphviz would be a bit overkill :). Being able to list phases could still be cool :)
Thinking more about this now I realize that just having a way to list the phases would be great and probably not difficult to implement.
On another note,
What do you think if it would be possible to add documentation to custom phases?
I realize that the name of the phases acts as a short documentation but
what if we could write a short description documenting why the phase
is needed?
Then, when we list the phases we could also list the documentation for that phase.
overkill? bloat?
all best,
jgart
prev parent reply other threads:[~2022-12-05 16:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 21:32 guix graph build phases jgart
2022-11-22 21:34 ` jgart
2022-11-22 22:12 ` Julien Lepiller
2022-11-22 22:43 ` jgart
2022-11-23 6:12 ` Julien Lepiller
2022-11-23 7:09 ` jgart
2022-11-23 7:11 ` jgart
2022-11-23 7:29 ` jgart
2022-12-05 16:10 ` jgart [this message]
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=20221205101043.GC26516@dismail.de \
--to=jgart@dismail.de \
--cc=guix-devel@gnu.org \
--cc=julien@lepiller.eu \
/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).