public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Michael Opdenacker <michael.opdenacker@bootlin.com>,
	 bitbake-devel@lists.openembedded.org
Cc: docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH] doc: Document FILE_LAYERNAME
Date: Tue, 20 Jun 2023 23:27:53 +0100	[thread overview]
Message-ID: <d3339edca72c52a5f4bd15e67f37cf8717ef607a.camel@linuxfoundation.org> (raw)
In-Reply-To: <60145e50-fd6a-b28c-51ab-f3cf3540f4a5@bootlin.com>

On Tue, 2023-06-20 at 22:16 +0200, Michael Opdenacker wrote:
> Hi Richard
> 
> On 20.06.23 at 15:58, Richard Purdie wrote:
> > Document the new variable.
> > 
> > Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> > ---
> >   .../bitbake-user-manual-ref-variables.rst                    | 5 +++++
> >   1 file changed, 5 insertions(+)
> > 
> > diff --git a/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst b/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst
> > index ee5d7ba8d4..337cfa3ed5 100644
> > --- a/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst
> > +++ b/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst
> > @@ -1072,6 +1072,11 @@ overview of their function and contents.
> >         environment variable. The value is a colon-separated list of
> >         directories that are searched left-to-right in order.
> >   
> > +   :term:`FILE_LAYERNAME`
> > +      During parsing and task execution, this is set to the name of the
> > +      layer containing the recipe file. Code can use this to identify which
> > +      layer a recipe is from.
> > +
> >      :term:`GITDIR`
> >         The directory in which a local copy of a Git repository is stored
> >         when it is cloned.
> 
> 
> Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
> 
> If you can merge this commit quickly, I'll be able to include the Yocto 
> Manual one you submitted, referring to it.

Merged!

We may need to expand some of the documentation on this but I wanted to
at least have the basics.

Cheers,

Richard


      reply	other threads:[~2023-06-20 22:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-20 13:58 [PATCH] doc: Document FILE_LAYERNAME Richard Purdie
2023-06-20 20:16 ` [docs] " Michael Opdenacker
2023-06-20 22:27   ` Richard Purdie [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=d3339edca72c52a5f4bd15e67f37cf8717ef607a.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=docs@lists.yoctoproject.org \
    --cc=michael.opdenacker@bootlin.com \
    /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