All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anders Heimer <anders.heimer@est.tech>
To: openembedded-core@lists.openembedded.org
Cc: Anders Heimer <anders.heimer@est.tech>
Subject: [PATCH 0/2] package: replace copydebugsources shell pipelines with Popen
Date: Tue, 16 Jun 2026 10:25:14 +0200	[thread overview]
Message-ID: <20260616082516.1553768-1-anders.heimer@est.tech> (raw)

Continue the OE-Core shell=True cleanup in oe.package.

Replace the copydebugsources() shell pipelines with explicit Popen
chains using argv lists, env= for LC_ALL and cwd= for cpio. Also replace
the externalsrc mv shell glob with glob.glob(glob.escape(...)) so
metacharacters in the directory path are handled literally.

The first copy pipeline keeps the previous failure-tolerant behavior,
while the symlink fixup pipeline now checks each stage directly. Add
oeqa tests for normal copying, symlink dereferencing, multiple
-ffile-prefix-map entries, ignored source paths, and externalsrc
relocation.

Anders Heimer (2):
  package: replace copydebugsources shell pipelines with Popen
  oeqa/oelib: add copydebugsources tests

 meta/lib/oe/package.py                        |  63 +++--
 meta/lib/oeqa/selftest/cases/oelib/package.py | 220 ++++++++++++++++++
 2 files changed, 265 insertions(+), 18 deletions(-)
 create mode 100644 meta/lib/oeqa/selftest/cases/oelib/package.py



             reply	other threads:[~2026-06-16  8:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-16  8:25 Anders Heimer [this message]
2026-06-16  8:25 ` [PATCH 1/2] package: replace copydebugsources shell pipelines with Popen Anders Heimer
2026-06-16 12:12   ` [OE-core] " Paul Barker
2026-06-16 13:35     ` Anders Heimer
2026-06-16 13:42       ` Paul Barker
2026-06-16 13:44       ` Richard Purdie
2026-06-16 14:13         ` Anders Heimer
2026-06-16  8:25 ` [PATCH 2/2] oeqa/oelib: add copydebugsources tests Anders Heimer

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=20260616082516.1553768-1-anders.heimer@est.tech \
    --to=anders.heimer@est.tech \
    --cc=openembedded-core@lists.openembedded.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.