From: Anders Heimer <anders.heimer@est.tech>
To: openembedded-core@lists.openembedded.org
Cc: Anders Heimer <anders.heimer@est.tech>
Subject: [PATCH v2 0/2] package: replace copydebugsources shell pipelines
Date: Thu, 18 Jun 2026 09:19:06 +0200 [thread overview]
Message-ID: <cover.1781766061.git.anders.heimer@est.tech> (raw)
Replace the copydebugsources() sort/grep/sed shell pipeline with Python
filtering over the NUL-separated source list while keeping cpio for the
copy pass. Use an explicit prefix + "/" match before stripping the mapped
debug source prefix, replace the symlink fixup pipeline with os.walk()
plus cpio, use an argv-list mv for externalsrc relocation, and pass the
empty-directory find command as an argv list.
The externalsrc relocation keeps mv, but now with an argv list and
glob.glob(glob.escape(...)). This preserves the old shell "*" and mv
overwrite semantics.
The first cpio copy pass keeps the previous failure-tolerant behavior,
while the symlink fixup copy still reports cpio failures.
Benchmarks did not indicate regression.
Changes in v2:
- Replace sort/grep/sed filtering with Python filtering while keeping cpio.
- Preserve externalsrc mv behavior using argv-list mv.
- Add test coverage for filtering, copy failures, symlinks, and relocation.
Anders Heimer (2):
package: replace copydebugsources shell pipelines
oeqa/selftest: add copydebugsources tests
meta/lib/oe/package.py | 70 +++--
meta/lib/oeqa/selftest/cases/oelib/package.py | 274 ++++++++++++++++++
2 files changed, 322 insertions(+), 22 deletions(-)
create mode 100644 meta/lib/oeqa/selftest/cases/oelib/package.py
next reply other threads:[~2026-06-18 7:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-18 7:19 Anders Heimer [this message]
2026-06-18 7:19 ` [PATCH v2 1/2] package: replace copydebugsources shell pipelines Anders Heimer
2026-06-18 14:02 ` [OE-core] " Paul Barker
2026-06-18 7:19 ` [PATCH v2 2/2] oeqa/selftest: 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=cover.1781766061.git.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox