From: John Ripple <john.ripple@keysight.com>
To: openembedded-core@lists.openembedded.org
Cc: John Ripple <john.ripple@keysight.com>
Subject: [PATCH v2 0/3] Create selftest suite for go-vendor.bbclass
Date: Wed, 15 Jul 2026 09:20:06 -0600 [thread overview]
Message-ID: <20260715152011.3542412-1-john.ripple@keysight.com> (raw)
This patch series adds a selftest suit for the go-vendor.bbclass and
fixes a couple of bugs in the go-vendor.bbclass.
John Ripple (3):
go-vendor.bbclass: Fix test file exclusion and license propagation
oeqa/selftest: Add go-vendor.bbclass selftest suite
go-vendor.bbclass: Run vendor_unlink task under fakeroot
.../recipes-test/govendor/files/modules.txt | 6 +
.../govendor/go-vendor-src-uri_1.0.bb | 13 ++
.../govendor/govendor-real-test_1.0.bb | 20 +++
meta/classes/go-vendor.bbclass | 9 +-
meta/lib/oeqa/selftest/cases/govendor.py | 169 ++++++++++++++++++
5 files changed, 213 insertions(+), 4 deletions(-)
create mode 100644 meta-selftest/recipes-test/govendor/files/modules.txt
create mode 100644 meta-selftest/recipes-test/govendor/go-vendor-src-uri_1.0.bb
create mode 100644 meta-selftest/recipes-test/govendor/govendor-real-test_1.0.bb
create mode 100644 meta/lib/oeqa/selftest/cases/govendor.py
next reply other threads:[~2026-07-15 15:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 15:20 John Ripple [this message]
2026-07-15 15:20 ` [meta][PATCH v2 1/3] go-vendor.bbclass: Fix test file exclusion and license propagation John Ripple
2026-07-15 15:20 ` [meta][meta-selftest][PATCH v2 2/3] oeqa/selftest: Add go-vendor.bbclass selftest suite John Ripple
2026-07-16 14:08 ` [OE-core] " Mathieu Dubois-Briand
2026-07-15 15:20 ` [meta][PATCH v2 3/3] go-vendor.bbclass: Run vendor_unlink task under fakeroot John Ripple
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=20260715152011.3542412-1-john.ripple@keysight.com \
--to=john.ripple@keysight.com \
--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.