From: Alexander Kanavin <alex.kanavin@gmail.com>
To: Ross Burton <Ross.Burton@arm.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 1/5] insane.bbclass: add a SUMMARY/HOMEPAGE check (oe-core recipes only)
Date: Fri, 5 May 2023 18:51:25 +0200 [thread overview]
Message-ID: <CANNYZj_ynuqtXg_=A11cfd9-PNTamKcbVhKMCG7-98+g+PwLkg@mail.gmail.com> (raw)
In-Reply-To: <DAE64A67-C0E3-4880-AE19-357FED7695C4@arm.com>
On Fri, 5 May 2023 at 13:43, Ross Burton <Ross.Burton@arm.com> wrote:
> I’m torn over this and the maintainer check. I like that the checks are being done earlier so they don’t trip up in oe-selftest, but I don’t like that they’re errors.
>
> If I want to add a new recipe to core and use devtool, it will immediately fail to build with errors due to the summary, homepage, and maintainer fields being missing. For this reason, I believe these should be warnings: they tell you that something needs to be done, but you can focus first on making a recipe that *compiles* before having to write a nice summary.
No problem. I'll correct that.
Alex
prev parent reply other threads:[~2023-05-05 16:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 7:35 [PATCH 1/5] insane.bbclass: add a SUMMARY/HOMEPAGE check (oe-core recipes only) Alexander Kanavin
2023-04-27 7:35 ` [PATCH 2/5] selftest/distrodata: clean up exception lists in recipe maintainers test Alexander Kanavin
2023-04-27 7:35 ` [PATCH 3/5] insane.bbclass: add a RECIPE_MAINTAINER check (oe-core recipes only) Alexander Kanavin
2023-04-28 10:36 ` [OE-core] " Martin Jansa
2023-04-28 11:54 ` Alexander Kanavin
2023-04-27 7:35 ` [PATCH 4/5] dhcpcd: use git instead of tarballs Alexander Kanavin
2023-04-27 7:35 ` [PATCH 5/5] perl: patch out build paths from native binaries Alexander Kanavin
2023-05-05 11:43 ` [OE-core] [PATCH 1/5] insane.bbclass: add a SUMMARY/HOMEPAGE check (oe-core recipes only) Ross Burton
2023-05-05 16:51 ` Alexander Kanavin [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='CANNYZj_ynuqtXg_=A11cfd9-PNTamKcbVhKMCG7-98+g+PwLkg@mail.gmail.com' \
--to=alex.kanavin@gmail.com \
--cc=Ross.Burton@arm.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.