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: Wed, 23 Nov 2022 01:09:43 -0600 [thread overview]
Message-ID: <20221123010943.GB20744@dismail.de> (raw)
In-Reply-To: <D0F56B9A-EF19-4D3D-88A0-A85F3026FAE0@lepiller.eu>
On Wed, 23 Nov 2022 07:12:55 +0100 Julien Lepiller <julien@lepiller.eu> wrote:
> I don't get why you want a picture. Could you share an example of what it would look like?
I was just thinking of something like a flowchart for the build phases.
For example, python-build-system's phases as a flowchart in mermaidjs:
%% python-build-system phases
flowchart TB
unpack -->
ensure-no-mtimes-pre-1980 -->
enable-bytecode-determinism -->
ensure-no-cythonized-files -->
build -->
install -->
add-install-to-pythonpath -->
add-install-to-path -->
wrap -->
check -->
sanity-check -->
rename-pth-file -->
strip
Here's the rendered mermaid flowchart:
https://kroki.io/mermaid/svg/eNptjz0OwjAMhfeeIgujJdhgYeAMXMBNjGKRP8WuqnJ6SloRCeHt2Z_t9w4HUxb1OcE4cXAgiyhFUzwKyfAIebYeq5r7bTBrTamgfRqAq2makkyVIGWIypEEyqpOl_Pxg-wEjoFgXJRsdgSOlGrkxBL_nbHNDL_IwYMDSWeavy45iWII3z_oHOw90AxbqILq-8ovsg_bbK5YOmk9bSmbEkysC3ybG1PXZJGgqG9OO62VyxteU2aW
The above diagram can easily be rewritten in plantuml and plantuml supports ascii diagrams also but ymmv:
https://www.planttext.com/api/plantuml/svg/RL0x2iCm3DrrYbn0q6vj0YK7wUBOAX6nPMChbFJqTPmiXMxl8_6UD1OrMTVW0PJLKvSsdQFWjB9tMBQY5Bgd0BGvW7wLPEmoG4zIrame4ODoe8AfiklzTccUcJpXj2dPw0WTAUN0mYNyRDeMnXzo-69FfPejk4DyLCnIKxq_cN4EJmKrub4q6Pt_U8VwpYQTotOckvou667Ti4cLvjes42QTMubzG3EdORyv9e2HnDK7VG40
@startuml
title python-build-system \n
start
:unpack;
:ensure-no-mtimes-pre-1980;
:enable-bytecode-determinism;
:ensure-no-cythonized-files;
:build -->;
:install -->;
:add-install-to-pythonpath;
:add-install-to-path;
:wrap -->;
:check -->;
:sanity-check;
:rename-pth-file;
:strip;
stop
@enduml
Where you thinking of capturing different information about the phases?
next prev parent reply other threads:[~2022-11-23 7:10 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 [this message]
2022-11-23 7:11 ` jgart
2022-11-23 7:29 ` jgart
2022-12-05 16:10 ` jgart
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=20221123010943.GB20744@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).