All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <adrian.freihofer@siemens.com>, <docs@lists.yoctoproject.org>
Subject: Re: [docs] [PATCH 2/4] conf.py: enable sphinx.ext.graphviz extension
Date: Tue, 22 Sep 2026 10:47:07 +0200	[thread overview]
Message-ID: <DLLPQC2GSTR8.2EVI8ZYZL5J1E@bootlin.com> (raw)
In-Reply-To: <DLLP3P6UGBWU.5MIE87WD6FE@bootlin.com>

On Tue Sep 22, 2026 at 10:17 AM CEST, Antonin Godard wrote:
> Hi,
>
> On Fri Sep 11, 2026 at 5:07 PM CEST, Adrian Freihofer via lists.yoctoproject.org wrote:
>> From: Adrian Freihofer <adrian.freihofer@siemens.com>
>>
>> Required by the .. graphviz:: diagrams added to dev-manual/devtool.rst
>> in a following commit.
>>
>> Signed-off-by: Adrian Freihofer <adrian.freihofer@siemens.com>
>> ---
>>  documentation/conf.py | 1 +
>>  1 file changed, 1 insertion(+)
>>
>> diff --git a/documentation/conf.py b/documentation/conf.py
>> index 48d28a686..7144d6db1 100644
>> --- a/documentation/conf.py
>> +++ b/documentation/conf.py
>> @@ -48,6 +48,7 @@ needs_sphinx = "4.0"
>>  extensions = [
>>      'sphinx.ext.autosectionlabel',
>>      'sphinx.ext.extlinks',
>> +    'sphinx.ext.graphviz',
>>      'sphinx.ext.intersphinx',
>>      'sphinx_copybutton',
>>      'sphinxcontrib.rsvgconverter',
>
> In order to add this extension, we also need to update our standards.md document
> to mention the usage of these types of graphics (under "## Adding new
> diagrams"). Also, we need to explain how to edit these graphs - did you use
> software to create them? Which one?
>
> Unrelated, but your series does not apply to master anymore, sorry :/ Could you
> rebase it?

We would also need to update our host requirements for building the
documentation as this extension requires 'dot':

  WARNING: dot command 'dot' cannot be run (needed for graphviz output), check the graphviz_dot setting

So this makes this addition more challenging, as we'll also need to update all
Autobuilder workers to include graphviz. It's possible, of course, but it's
going to take some time.

An alternative I've considered in the past is the addition of the
sphinxcontrib-mermaid extension[1] to our docs. The main advantage I see using
this is that mermaid diagrams are much simpler to read and understand when
reading them textually, so also more maintainable. It looks also slightly more
modern, and has more possibilities, like having our own color theme, etc. Also,
as far as I've tested it, it does not require any additional host dependencies,
it is self-contained.

What do you think?

Can your series be re-sent without graphviz diagrams? And we work on refreshing
diagrams separately, later.

In any case, if this series needs to be merged before 6.1, it would need to be
one without graphviz or mermaid diagrams, as both take time to integrate.

[1]: https://github.com/mgaitan/sphinxcontrib-mermaid

Thanks!
Antonin


  reply	other threads:[~2026-09-22  8:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-11 15:07 [PATCH 1/4] dev-manual/devtool: fix non-patch local file handling docs AdrianF
2026-09-11 15:07 ` [PATCH 2/4] conf.py: enable sphinx.ext.graphviz extension AdrianF
2026-09-22  8:17   ` [docs] " Antonin Godard
2026-09-22  8:47     ` Antonin Godard [this message]
2026-09-24 19:32       ` Freihofer, Adrian
2026-09-11 15:07 ` [PATCH 3/4] dev-manual/devtool: update devtool ide-sdk section for recent features AdrianF
2026-09-22  8:18 ` [docs] [PATCH 1/4] dev-manual/devtool: fix non-patch local file handling docs Antonin Godard

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=DLLPQC2GSTR8.2EVI8ZYZL5J1E@bootlin.com \
    --to=antonin.godard@bootlin.com \
    --cc=adrian.freihofer@siemens.com \
    --cc=docs@lists.yoctoproject.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.
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.