From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: "YP docs mailing list" <docs@lists.yoctoproject.org>,
"BitBake developer list" <bitbake-devel@lists.openembedded.org>
Subject: Re: [docs] [PATCH] Mention existence of three supported "classes" directories
Date: Tue, 08 Jul 2025 13:48:50 +0200 [thread overview]
Message-ID: <DB6NF7YH17U9.6HYVT80TCPK8@bootlin.com> (raw)
In-Reply-To: <f2ab85c5-e703-ebf2-7c97-9ebe1353f817@crashcourse.ca>
On Tue Jul 8, 2025 at 1:42 PM CEST, Robert P. J. Day wrote:
> On Tue, 8 Jul 2025, Antonin Godard via lists.yoctoproject.org wrote:
>
>> On Tue Jul 8, 2025 at 1:29 PM CEST, Robert P. J. Day wrote:
>> >
>> > Early in Section 1, mention that BitBake supports three related
>> > classes directories.
>> >
>> > Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
>> >
>> > ---
>> >
>> > I'm not thrilled with this explanation in terms of where it is, but
>> > it's better than not explaining this at all.
>> >
>> > diff --git a/doc/bitbake-user-manual/bitbake-user-manual-intro.rst b/doc/bitbake-user-manual/bitbake-user-manual-intro.rst
>> > index 539bb62d8..feab1df9d 100644
>> > --- a/doc/bitbake-user-manual/bitbake-user-manual-intro.rst
>> > +++ b/doc/bitbake-user-manual/bitbake-user-manual-intro.rst
>> > @@ -206,6 +206,18 @@ installing (empty by default) and packaging (empty by default). These
>> > tasks are often overridden or extended by other classes added during the
>> > project development process.
>> >
>> > +.. note::
>> > +
>> > + While BitBake comes with just the one ``base.bbclass`` file in the
>> > + ``classes`` directory, it supports class files also being installed
>> > + in related directories ``classes-global`` and ``classes-recipe`` and
>> > + will automatically search all three directories for a selectd class
>>
>> s/selectd/selected/
>
> already submitted that fix.
>
>> > + file.
>> > +
>> > + This means that, in this documentation, when you see a reference to
>> > + class files being in the ``classes`` directory, you can interpret that
>> > + as meaning in any one of the above three directories.
>>
>> I don't think this is enough explanation on these directories, and as-is it
>> would create confusion I think.
>>
>> There are some details about these directories here:
>> https://bootlin.com/doc/training/yocto/yocto-slides.pdf#19
>>
>> Maybe that can help you add the explanation?
>>
>> I would also explain the difference between these directories (classes,
>> classes-recipe and classes-global) in a paragraph of its own, not in a note.
>
> Except that, once again, we would be going outside the bounds of
> BitBake. I totally agree that there should be a comprehensive
> explanation of these directories, but where does that belong?
I think that saying:
- classes-recipe is meant for recipes, and are inherited through the
`inherit` directive
- classes-global is meant to be inherited through the `INHERIT` variable
- classes can be used in both context
should not be out-of-boundary.
Antonin
--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2025-07-08 11:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 11:29 [PATCH] Mention existence of three supported "classes" directories Robert P. J. Day
2025-07-08 11:37 ` [docs] " Antonin Godard
2025-07-08 11:42 ` Robert P. J. Day
2025-07-08 11:48 ` 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=DB6NF7YH17U9.6HYVT80TCPK8@bootlin.com \
--to=antonin.godard@bootlin.com \
--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