Openembedded Bitbake Development
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: ross.burton@arm.com, "ticotimo@gmail.com" <ticotimo@gmail.com>
Cc: "bitbake-devel@lists.openembedded.org"
	<bitbake-devel@lists.openembedded.org>
Subject: Re: [bitbake-devel] [PATCH] parse: only search each BBPATH directory once in include_all
Date: Tue, 20 Oct 2026 13:30:47 +0100	[thread overview]
Message-ID: <7f00a969c9ef34a77342ca8909def148aceeb652.camel@linuxfoundation.org> (raw)
In-Reply-To: <6C7FAEF1-2BE9-4E2C-B2DF-A037491D00D0@arm.com>

On Mon, 2026-10-19 at 16:12 +0000, Ross Burton via
lists.openembedded.org wrote:
> On 19 Oct 2026, at 03:04, Tim Orling via lists.openembedded.org
> <ticotimo=gmail.com@lists.openembedded.org> wrote:
> > 
> > +        for path in
> > dict.fromkeys(data.getVar("BBPATH").split(":")):
> 
> Feels like using a set() instead of dict.fromkeys() would be neater.

Ordering matters here...

Cheers,

Richard

  reply	other threads:[~2026-10-20 12:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-19  2:04 [PATCH] parse: only search each BBPATH directory once in include_all Tim Orling
2026-10-19 16:12 ` [bitbake-devel] " Ross Burton
2026-10-20 12:30   ` Richard Purdie [this message]
2026-10-20 12:33     ` Ross Burton
2026-10-20 12:46       ` Richard Purdie
2026-10-20 12:32 ` Richard Purdie
2026-10-26  0:20 ` [PATCH v2 0/2] Handle duplicate BBPATH entries Tim Orling
2026-10-26  0:20 ` [PATCH v2 1/2] parse: only search each BBPATH directory once in include_all Tim Orling
2026-10-26  0:20 ` [PATCH v2 2/2] cookerdata: error on duplicate BBPATH entries Tim Orling
2026-11-02  7:46   ` [bitbake-devel] " Mathieu Dubois-Briand

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=7f00a969c9ef34a77342ca8909def148aceeb652.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=ross.burton@arm.com \
    --cc=ticotimo@gmail.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