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] dev-manual: add second way to assign "PV" for external SCM
Date: Tue, 16 Jun 2026 15:34:36 +0200 [thread overview]
Message-ID: <DJAIH1ZSQRDF.2RZZVZEHU1OYO@bootlin.com> (raw)
In-Reply-To: <f1c6733a-a659-a78d-1b41-474b3103328e@crashcourse.ca>
Hi,
On Fri Jun 12, 2026 at 9:58 AM CEST, Robert P. J. Day wrote:
>
> In addition to hard-coding a PV value in the context of an external
> SCM, show also just appending the string "+git" to the value already
> calculated for PV.
>
> Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
>
> ---
>
> diff --git a/documentation/dev-manual/external-scm.rst b/documentation/dev-manual/external-scm.rst
> index 3ca9079b3..4492de9cd 100644
> --- a/documentation/dev-manual/external-scm.rst
> +++ b/documentation/dev-manual/external-scm.rst
> @@ -13,9 +13,12 @@ Subversion (SVN) and Git.
>
> To enable this behavior, the :term:`PV` of
> the recipe needs to include a ``+`` sign in its assignment.
> -Here is an example::
> +Here are a couple examples of how this can be done --- the first
> +hard-coding the value for ``PV``, the second simply appending
> +the string "+git" to the value already assigned to that variable::
s/already assigned/already extracted from the recipe file name/ ?
This is why you'd append, I don't see any other instances.
>
> PV = "1.2.3+git"
> + PV .= "+git"
>
> :term:`Bitbake` later includes the source control information in :term:`PKGV`
> during the packaging phase.
Antonin
prev parent reply other threads:[~2026-06-16 13:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-12 7:58 [PATCH] dev-manual: add second way to assign "PV" for external SCM Robert P. J. Day
2026-06-16 13: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=DJAIH1ZSQRDF.2RZZVZEHU1OYO@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