From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: alex.kanavin@gmail.com, reatmon@ti.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core][PATCH] package: Add support for INSANE_SKIP for incompatible-license
Date: Tue, 16 Jul 2024 10:00:46 +0100 [thread overview]
Message-ID: <c669ae7c3316ad33931bc9c40bb9c49e8af1895e.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj9DXbuFwHLHZa2p8asasehxkDaGYoH+PuMWEbfiHFx20g@mail.gmail.com>
On Tue, 2024-07-16 at 09:57 +0200, Alexander Kanavin via
lists.openembedded.org wrote:
> On Mon, 15 Jul 2024 at 21:07, Ryan Eatmon via lists.openembedded.org
> <reatmon=ti.com@lists.openembedded.org> wrote:
> >
> > With the move to make more warnings into errors it is inevitable
> > that we
> > will need more hooks to skip the errors on a recipe by recipe
> > basis.
> > This patch just adds INSANE_SKIP support for the incompatible-
> > license check.
>
> I do not think this is a good idea. This was a warning before, the
> warning was never fixed, and now, instead of addressing the issue,
> the
> error should be suppressed so that it's *never* going to be fixed?
>
> You can still revert to a warning if you so wish, but in general,
> global INCOMPATIBLE_LICENSE is essentialy deprecated in favour a
> per-image one, is there a reason you are still using that?
The ERROR_QA change is going to take a bit of adjustment for people.
There are some things in there which recipes will need to tweak for
various reasons (e.g. pre-built binaries). After much thought, I (and
others) concluded it was better to have recipes marked up with the
issues rather than have it as some "random" warning in the build people
ignored. I therefore think it is the right move but we need to support
people in marking up the recipes (and ultimately ideally fixing some of
the issues).
With regard to the patch, I think the key question is whether we want
to add INSANE_SKIP support to every call site (potentially) or whether
there is some better function abstraction we can use.
The implementation in do_package_qa is:
skip = set((d.getVar('INSANE_SKIP') or "").split() +
(d.getVar('INSANE_SKIP:' + package) or "").split())
which shows the first issue with this patch - INSANE_SKIP itself isn't
looked at (for a recipe wide disable).
So I think we need a new common function alongside oe.qa.handle_error()
which adds the pkg option and checks accordingly?
Cheers,
Richard
next prev parent reply other threads:[~2024-07-16 9:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 19:07 [OE-core][PATCH] package: Add support for INSANE_SKIP for incompatible-license Ryan Eatmon
2024-07-16 7:57 ` Alexander Kanavin
2024-07-16 9:00 ` Richard Purdie [this message]
[not found] ` <17E2A5EE047FA37E.16356@lists.openembedded.org>
2024-07-16 9:43 ` Richard Purdie
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=c669ae7c3316ad33931bc9c40bb9c49e8af1895e.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=reatmon@ti.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