Yocto Project Documentation
 help / color / mirror / Atom feed
From: Quentin Schulz <quentin.schulz@cherry.de>
To: rpjday@crashcourse.ca,
	YP docs mailing list <docs@lists.yoctoproject.org>
Cc: "bitbake-devel@lists.openembedded.org"
	<bitbake-devel@lists.openembedded.org>
Subject: Re: [docs] [PATCH] clarify how bbappend files work with an unversioned BitBake recipe
Date: Mon, 2 Jun 2025 15:57:39 +0200	[thread overview]
Message-ID: <37097686-48e5-4a0b-93fa-62152fe50dc0@cherry.de> (raw)
In-Reply-To: <562c3a8a-2cfd-a4cc-7dc8-0126b5b02a86@crashcourse.ca>

Hi Robert,

Please Cc the bitbake ML as well. The Yocto docs community reviews the 
patches but it's up to the BitBake maintainer(s) to take the patch.

C.f. https://git.openembedded.org/bitbake/tree/README#n29

On 6/2/25 3:28 PM, Robert P. J. Day via lists.yoctoproject.org 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``.
> +

I wouldn't make this a note. There are a bunch of examples, all of which 
aren't in a note, so we should do the same here.

I could even see this being mentioned in an even sneakier way, e.g.:

"""
BitBake expects every append file to have a corresponding recipe file 
(e.g. ``formfactor.bb`` and ``formfactor.bbappend``).
"""

What follows in this paragraph is actually pretty explanatory I believe? 
"The append file and corresponding recipe file must use the same root 
filename. The filenames can only differ in the file type".

Though we contradict ourselves a few paragraphs below where we say we 
can use % to do some less strict matching :)

Cheers,
Quentin


  reply	other threads:[~2025-06-02 13:57 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 ` Quentin Schulz [this message]
2025-06-04  7:34 ` [docs] " Antonin Godard

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=37097686-48e5-4a0b-93fa-62152fe50dc0@cherry.de \
    --to=quentin.schulz@cherry.de \
    --cc=bitbake-devel@lists.openembedded.org \
    --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