From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <quentin.schulz@cherry.de>, <foss@0leil.net>,
<bitbake-devel@lists.openembedded.org>
Cc: "Robert P. J. Day" <rpjday@crashcourse.ca>,
<docs@lists.yoctoproject.org>
Subject: Re: [docs] [PATCH 3/4] doc: bitbake-user-manual-ref-variables: clarify BBMASK matching patterns
Date: Mon, 16 Feb 2026 09:02:59 +0100 [thread overview]
Message-ID: <DGG89S39J5AT.3JD08TH092QC3@bootlin.com> (raw)
In-Reply-To: <f97528ec-917d-44d8-be42-ab0c48a1b2cc@cherry.de>
Hi,
On Thu Feb 12, 2026 at 12:38 PM CET, Quentin Schulz via lists.yoctoproject.org wrote:
[...]
>> So this looks this is actually what most users want to do, right? Wouldn't it be
>> better to put this forward instead of in a note, say, at the beginning of the
>> definition?
>>
>> For example, replacing the first example in the variable's definition by:
>>
>> -The following example uses a complete regular expression to tell
>> -BitBake to ignore all recipe and recipe append files in the
>> -``meta-ti/recipes-misc/`` directory::
>> -
>> - BBMASK = "meta-ti/recipes-misc/"
>> +The following example uses a complete regular expression to tell BitBake to
>> +ignore all recipe and recipe append files in the ``recipes-misc/`` directory
>> +and subdirectories of the ``meta-ti`` layer::
>> +
>> + BBMASK = "${BBFILE_PATTERN_meta-ti}/recipes-bsp/"
>>
>
> Yeah I was conflicted... not sure what's best. This does also rely on
> BBFILE_PATTERN_meta-ti starting with ^ otherwise we have another
> potential name clash and we don't actually mention that in the
> documentation of BBFILE_PATTERN (though it is set like that when
> creating a layer with bitbake-layers create-layer).
>
> If for some reason you have:
>
> /layers/meta-ti/recipes-bsp
> /downstream/my-layer/appends/layers/meta-ti/recipes-bsp
>
> then both would be matched (I assume, I haven't checked). That is very
> much a corner case.
>
> I'm also pretty sure nobody actually does that. The only layer I have in
> my pool of cloned layers which uses BBMASK is meta-lts-mixins and then
> doesn't even have the layer name in the paths so /me shrugs.
>
>> What do you think?
>>
>
> We could start with the BBFILE_PATTERN thingy, then explain there are
> other less restrictive ways to match multiple recipes or directories
> from different locations later on.
Yes, I think we should do that
Antonin
next prev parent reply other threads:[~2026-02-16 8:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 18:06 [PATCH 0/4] doc: bitbake-user-manual-ref-variables: clarify BBMASK examples Quentin Schulz
2026-02-11 18:06 ` [PATCH 1/4] doc: bitbake-user-manual-ref-variables: clarify BBMASK directory matching Quentin Schulz
2026-02-12 8:49 ` [docs] " Antonin Godard
2026-02-12 11:12 ` Quentin Schulz
2026-02-11 18:06 ` [PATCH 2/4] doc: bitbake-user-manual-ref-variables: have directory examples be consistent Quentin Schulz
2026-02-11 18:06 ` [PATCH 3/4] doc: bitbake-user-manual-ref-variables: clarify BBMASK matching patterns Quentin Schulz
2026-02-12 8:58 ` [docs] " Antonin Godard
2026-02-12 11:38 ` Quentin Schulz
2026-02-16 8:02 ` Antonin Godard [this message]
2026-02-11 18:06 ` [PATCH 4/4] doc: bitbake-user-manual-ref-variables: update BBMASK example with current meta-ti Quentin Schulz
2026-02-11 20:45 ` [docs] [PATCH 0/4] doc: bitbake-user-manual-ref-variables: clarify BBMASK examples Robert P. J. Day
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=DGG89S39J5AT.3JD08TH092QC3@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=docs@lists.yoctoproject.org \
--cc=foss@0leil.net \
--cc=quentin.schulz@cherry.de \
--cc=rpjday@crashcourse.ca \
/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.