Yocto Meta Virtualization
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@gmail.com>
To: meta-virtualization@lists.yoctoproject.org
Subject: Re: [meta-virtualization][RFC][PATCH 1/5] vcontainer-bbmask.inc: add python3-pexpect,-ptyprocess
Date: Tue, 28 Jul 2026 10:47:14 -0700 (PDT)	[thread overview]
Message-ID: <6a68eb22.e28fa2c5.219bbc.346d@mx.google.com> (raw)
In-Reply-To: <20260727000247.1623785-3-tim.orling@konsulko.com>

Thanks Tim. I'm taking 2/5 through 5/5 directly (verified 2/5 against
image-oci.bbclass — the auto-fold of OCI_LAYERS `packages:` entries
into IMAGE_INSTALL at line ~389 is exactly the duplication this drops,
so it's a clean removal). 3/5's added deps all trace to concrete
failures documented in 5/5, which is a great artifact.

One question before I take this one:

The commit says python3-pexpect is needed "during run-time testing
with the bitbake-setup workflow." What in the built container actually
imports/exec's pexpect at runtime? If it's the vcontainer test suite
driving the container from outside, pexpect belongs on the test host,
not baked into the image. If it's something inside the container —
bitbake-setup itself, a Yocto tool, or a test harness that runs
in-container — that's legitimate, but a one-line note in the commit
message naming the caller would help future readers understand why
we're carving a hole in the meta-python mask.

If it's just needed for our own vcontainer test runner and not by
anything the container itself invokes, I'd rather leave the meta-python
mask intact and put pexpect on the host that runs the tests.

Bruce


  parent reply	other threads:[~2026-07-28 17:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-27  0:02 [meta-virtualization][RFC][PATCH 1/5] vcontainer-bbmask.inc: add python3-pexpect,-ptyprocess tim.orling
2026-07-27  0:02 ` [meta-virtualization][RFC][PATCH 2/5] container-yocto-builder: drop redundant IMAGE_INSTALL tim.orling
2026-07-28 17:47   ` Bruce Ashfield
2026-07-27  0:02 ` [meta-virtualization][RFC][PATCH 3/5] packagegroup-yocto-builder: add additional dependencies tim.orling
2026-07-28 17:47   ` Bruce Ashfield
2026-07-27  0:02 ` [meta-virtualization][RFC][PATCH 4/5] container-image-multiarch: add container-yocto-builder tim.orling
2026-07-28 17:47   ` Bruce Ashfield
2026-07-27  0:02 ` [meta-virtualization][RFC][PATCH 5/5] docs: add container-yocto-builder.md tim.orling
2026-07-28 17:47   ` Bruce Ashfield
2026-07-30 13:41   ` [PATCH v2 " tim.orling
2026-07-28 17:47 ` Bruce Ashfield [this message]
2026-07-29 21:25   ` [meta-virtualization][RFC][PATCH 1/5] vcontainer-bbmask.inc: add python3-pexpect,-ptyprocess Tim Orling
2026-07-30 13:40 ` [PATCH v2 " tim.orling

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=6a68eb22.e28fa2c5.219bbc.346d@mx.google.com \
    --to=bruce.ashfield@gmail.com \
    --cc=meta-virtualization@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox