From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: "Joshua Watt" <JPEWhacker@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core][PATCH] classes/sanity: Add comment about github & gitlab archives
Date: Thu, 4 Aug 2022 22:58:14 +0200 [thread overview]
Message-ID: <20220804225814.61baffe2@booty> (raw)
In-Reply-To: <20220804145831.1545698-1-JPEWhacker@gmail.com>
Hi Joshua,
On Thu, 4 Aug 2022 09:58:31 -0500
"Joshua Watt" <JPEWhacker@gmail.com> wrote:
> Add a comment so that users grepping for "github" or "gitlab" will find
> this code (since the regex wont).
>
> Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
> ---
> meta/classes/insane.bbclass | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/meta/classes/insane.bbclass b/meta/classes/insane.bbclass
> index 37e10ad850..c8b434bb54 100644
> --- a/meta/classes/insane.bbclass
> +++ b/meta/classes/insane.bbclass
> @@ -1335,6 +1335,7 @@ def unpack_check_src_uri(pn, d):
> oe.qa.handle_error("src-uri-bad", "%s: SRC_URI uses PN not BPN" % pn, d)
>
> for url in d.getVar("SRC_URI").split():
> + # Search for github and gitlab URLs that pull unstable archives (comment for future greppers)
> if re.search(r"git(hu|la)b\.com/.+/.+/archive/.+", url):
I think the regexp is unnecessarily baroque and it could become just a
more readable (github|gitlab). And that would add only 4 chars! :-)
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2022-08-04 20:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 14:58 [OE-core][PATCH] classes/sanity: Add comment about github & gitlab archives Joshua Watt
2022-08-04 20:58 ` Luca Ceresoli [this message]
2022-08-04 21:04 ` Joshua Watt
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=20220804225814.61baffe2@booty \
--to=luca.ceresoli@bootlin.com \
--cc=JPEWhacker@gmail.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.