From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/DTS Bug 1757] Remove optional poetry docs build workflow
Date: Fri, 18 Jul 2025 21:07:40 +0000 [thread overview]
Message-ID: <bug-1757-3@https.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1174 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1757
Bug ID: 1757
Summary: Remove optional poetry docs build workflow
Product: DPDK
Version: 25.03
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: minor
Priority: Normal
Component: DTS
Assignee: dev@dpdk.org
Reporter: probb@iol.unh.edu
CC: juraj.linkes@pantheon.tech, probb@iol.unh.edu
Target Milestone: ---
Currently there are two docs workflows available for DTS - the "normal" DPDK
build workflow like:
meson setup my-build
ninja -C my-build doc
And this is totally satisfactory for our purposes.
There is also an alternate docs build process through poetry which is explained
in dts.rst. But, the build result "improvements" for using this are minor and
the downsides associated with promoting this workflow (instead of just
directing people to the standard docs build process) are significant. So, let's
remove this poetry dts docs build explanation from dts.rst.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3137 bytes --]
reply other threads:[~2025-07-18 21:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-1757-3@https.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.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 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 NNTP newsgroup(s).