($INBOX_DIR/description missing)
 help / color / mirror / Atom feed
From: Quentin Schulz <foss+yocto@0leil.net>
To: Joshua Watt <JPEWhacker@gmail.com>,
	 Richard Purdie <richard.purdie@linuxfoundation.org>,
	 docs@lists.yoctoproject.org
Cc: Quentin Schulz <quentin.schulz@cherry.de>,
	 Quentin Schulz <foss+yocto@0leil.net>
Subject: [PATCH] docs: brief-yoctoprojectqs: explicit version dependency on websockets python module
Date: Fri, 03 May 2024 19:07:45 +0200	[thread overview]
Message-ID: <20240503-websockets-module-v1-1-4065c348276d@cherry.de> (raw)

From: Quentin Schulz <quentin.schulz@cherry.de>

We now check that the websockets module version is at least 9.1 in
bitbake itself so we can specify more precisely what "recent version"
means.

While at it, list which distributions have a recent enough websockets
python module in their package feed and give some hint at how to support
other distributions.

Cc: Quentin Schulz <foss+yocto@0leil.net>
Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
This is done according to the pending patch:
https://lore.kernel.org/bitbake-devel/20240502183516.1216885-1-JPEWhacker@gmail.com/T/#u

Still wondering if we should add this to poky.yaml.in as a "hard"
dependency? If we do, how do we plan to handle distros which do not have
(a recent enough) websockets python module?
---
 documentation/brief-yoctoprojectqs/index.rst | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/documentation/brief-yoctoprojectqs/index.rst b/documentation/brief-yoctoprojectqs/index.rst
index 4301bfd97..c5400e4ac 100644
--- a/documentation/brief-yoctoprojectqs/index.rst
+++ b/documentation/brief-yoctoprojectqs/index.rst
@@ -256,8 +256,11 @@ an entire Linux distribution, including the toolchain, from source.
          BB_HASHSERVE = "auto"
          BB_SIGNATURE_HANDLER = "OEEquivHash"
 
-      The hash equivalence server needs a recent version of python
-      websockets installed to work correctly.
+      The hash equivalence server needs the websockets python module version 9.1
+      or later. Debian GNU/Linux 12 (Bookworm) and later, Fedora, CentOS Stream
+      9 and later, and Ubuntu 22.04 (LTS) and later, all have a recent enough
+      package. Other supported distributions need to get the module some other
+      place than their package feed, e.g. via ``pip``.
 
 #. **Start the Build:** Continue with the following command to build an OS
    image for the target, which is ``core-image-sato`` in this example:

---
base-commit: 291dae69b7ecc5ae49f378a7098c1187c820765b
change-id: 20240503-websockets-module-d6fba12a4171

Best regards,
-- 
Quentin Schulz <quentin.schulz@cherry.de>



             reply	other threads:[~2024-05-03 17:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-03 17:07 Quentin Schulz [this message]
2024-05-09 10:59 ` [PATCH] docs: brief-yoctoprojectqs: explicit version dependency on websockets python module Richard Purdie
2024-05-13  8:02   ` Quentin Schulz

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=20240503-websockets-module-v1-1-4065c348276d@cherry.de \
    --to=foss+yocto@0leil.net \
    --cc=JPEWhacker@gmail.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=quentin.schulz@cherry.de \
    --cc=richard.purdie@linuxfoundation.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 read-only IMAP folder(s) and NNTP newsgroup(s).