From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: peter.kjellerstedt@axis.com, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 2/2] Revert "insane.bbclass: Move test for invalid PACKAGECONFIGs to do_recipe_qa"
Date: Wed, 18 Mar 2026 23:38:19 +0000 [thread overview]
Message-ID: <9fe457c2fae233e5c6821cc2ced1758f58ae883c.camel@linuxfoundation.org> (raw)
In-Reply-To: <20260318215934.1949404-2-pkj@axis.com>
Hi Peter,
On Wed, 2026-03-18 at 22:59 +0100, Peter Kjellerstedt via lists.openembedded.org wrote:
> This reverts commit d3325c384a7df54c564cae093659cf7b692629f2.
>
> Moving the QA test for invalid PACKAGECONFIGs to the recipe_qa task
> turned out to be a bad idea as that task is expected to be architecture
> independent. So move it back to the qa_configure function. The original
> problem (that the configure task is not run for packagegroups) will have
> to be solved in packagegroup.bbclass instead.
>
> Signed-off-by: Peter Kjellerstedt <pkj@axis.com>
> ---
> meta/classes-global/insane.bbclass | 20 ++++++++++----------
> 1 file changed, 10 insertions(+), 10 deletions(-)
>
> diff --git a/meta/classes-global/insane.bbclass b/meta/classes-global/insane.bbclass
> index aeffee7983..7b13e932ff 100644
> --- a/meta/classes-global/insane.bbclass
> +++ b/meta/classes-global/insane.bbclass
> @@ -1423,6 +1423,16 @@ Rerun configure task after fixing this."""
> except subprocess.CalledProcessError:
> pass
>
> + # Check invalid PACKAGECONFIG
> + pkgconfigs = (d.getVar("PACKAGECONFIG") or "").split()
> + if pkgconfigs:
> + pkgconfigflags = d.getVarFlags("PACKAGECONFIG") or {}
> + invalid_pkgconfigs = set(pkgconfigs) - set(pkgconfigflags)
> + if invalid_pkgconfigs:
> + pn = d.getVar('PN')
> + error_msg = "%s: invalid PACKAGECONFIG(s): %s" % (pn, " ".join(sorted(invalid_pkgconfigs)))
> + oe.qa.handle_error("invalid-packageconfig", error_msg, d)
> +
> oe.qa.exit_if_errors(d)
> }
>
> @@ -1484,21 +1494,11 @@ python do_recipe_qa() {
> if re.search(r"git(hu|la)b\.com/.+/.+/archive/.+", url) or "//codeload.github.com/" in url:
> oe.qa.handle_error("src-uri-bad", "%s: SRC_URI uses unstable GitHub/GitLab archives, convert recipe to use git protocol" % pn, d)
>
> - def test_packageconfig(pn, d):
> - pkgconfigs = (d.getVar("PACKAGECONFIG") or "").split()
> - if pkgconfigs:
> - pkgconfigflags = d.getVarFlags("PACKAGECONFIG") or {}
> - invalid_pkgconfigs = set(pkgconfigs) - set(pkgconfigflags)
> - if invalid_pkgconfigs:
> - error_msg = "%s: invalid PACKAGECONFIG(s): %s" % (pn, " ".join(sorted(invalid_pkgconfigs)))
> - oe.qa.handle_error("invalid-packageconfig", error_msg, d)
> -
> pn = d.getVar('PN')
> test_naming(pn, d)
> test_missing_metadata(pn, d)
> test_missing_maintainer(pn, d)
> test_srcuri(pn, d)
> - test_packageconfig(pn, d)
> oe.qa.exit_if_errors(d)
> }
Thanks for sending this. Atfer a bit of thought, I have a slightly
different idea which might be worth a try, perhaps we can put the
PACKAGECONFIG code into a function in lib/oe/qa.py and then call it
from the configure postfunc but also as a postfunc in one of the
packagegroup tasks?
I'd prefer not to reinstate the configure task if we can help it as
those tasks have "special" meanings and it is safer to remove
everything consistently if we can.
Cheers,
Richard
prev parent reply other threads:[~2026-03-18 23:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 21:59 [PATCH 1/2] packagegroup.bbclass: Reinstate the configure task Peter Kjellerstedt
2026-03-18 21:59 ` [PATCH 2/2] Revert "insane.bbclass: Move test for invalid PACKAGECONFIGs to do_recipe_qa" Peter Kjellerstedt
2026-03-18 23:38 ` Richard Purdie [this message]
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=9fe457c2fae233e5c6821cc2ced1758f58ae883c.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.kjellerstedt@axis.com \
/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