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] should the YP docs mention layers.openembedded.org recipe advanced query?
Date: Tue, 16 Jun 2026 17:03:05 +0200 [thread overview]
Message-ID: <DJAKCT00PT9R.JMQ30E3ELKAS@bootlin.com> (raw)
In-Reply-To: <86b66622-c80e-9f67-0e21-0743b305032d@crashcourse.ca>
Hi,
On Tue Jun 16, 2026 at 12:18 PM CEST, Robert P. J. Day wrote:
>
> while transferring some ptest content from the ptest wiki page to
> the docs, i was reminded of the advanced query feature of recipes tab
> of the OE layers page:
>
> https://layers.openembedded.org/layerindex/branch/master/recipes/
>
> which that ptest wiki page mentioned toward the end:
>
> https://wiki.yoctoproject.org/wiki/Ptest#Recipes_with_ptest_Enabled
>
> as to how to list all recipes that inherited ptest if one wanted to
> see some examples:
>
> http://layers.openembedded.org/layerindex/branch/master/recipes/?q=inherits%3Aptest
>
> it occurred to me that that would be kind of a useful note to make in,
> say, the ref manual "classes" section -- to inform the reader how to
> find examples of recipes that inherit a given class to see how it's
> done.
>
> rather than add a note to the "classes" section, would it make more
> sense to add a more comprehensive section somewhere on how to use that
> advanced query feature and link to it when appropriate? or does that
> feature fall outside the scope of the YP docs?
Perhaps you can add a note in
documentation/dev-manual/new-recipe.rst:Locating and Using a Similar Recipe
I wouldn't dive into too much details though.
Antonin
prev parent reply other threads:[~2026-06-16 15:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-16 10:18 should the YP docs mention layers.openembedded.org recipe advanced query? Robert P. J. Day
2026-06-16 15:03 ` 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=DJAKCT00PT9R.JMQ30E3ELKAS@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 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.