From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>,
"YP docs mailing list" <docs@lists.yoctoproject.org>
Subject: Re: [docs] [PATCH] clarify how bbappend files work with an unversioned BitBake recipe
Date: Wed, 04 Jun 2025 09:34:14 +0200 [thread overview]
Message-ID: <DADKPRAZICS9.UPRP8FSQYDQ2@bootlin.com> (raw)
In-Reply-To: <562c3a8a-2cfd-a4cc-7dc8-0126b5b02a86@crashcourse.ca>
On Mon Jun 2, 2025 at 3:28 PM CEST, Robert P. J. Day wrote:
>
> Add a short note to the BitBake intro manual chapter to clarify that,
> given an unversioned .bb recipe file, the matching .bbappend must also
> be unversioned.
>
> Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
>
> ---
>
> diff --git a/doc/bitbake-user-manual/bitbake-user-manual-intro.rst b/doc/bitbake-user-manual/bitbake-user-manual-intro.rst
> index 539bb62d8..1c3faff0e 100644
> --- a/doc/bitbake-user-manual/bitbake-user-manual-intro.rst
> +++ b/doc/bitbake-user-manual/bitbake-user-manual-intro.rst
> @@ -272,6 +272,12 @@ append name would not match. However, if you named the append file
> In the most general case, you could name the append file something as
> simple as ``busybox_%.bbappend`` to be entirely version independent.
>
> +.. note::
> +
> + In the infrequent case of an unversioned BitBake recipe (such as
> + ``linux-yocto-dev.bb``), the corresponding append file must be similarly
> + unversioned; that is, ``linux-yocto-dev.bbappend``.
> +
> Obtaining BitBake
> =================
This needs to be sent to the bitbake-devel@lists.openembedded.org mailing list,
with this list in copy.
Thanks,
Antonin
--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2025-06-04 7:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-02 13:28 [PATCH] clarify how bbappend files work with an unversioned BitBake recipe Robert P. J. Day
2025-06-02 13:57 ` [docs] " Quentin Schulz
2025-06-04 7:34 ` Antonin Godard [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=DADKPRAZICS9.UPRP8FSQYDQ2@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox