Re: [docs] [PATCH v2] dev-manual: describe two ways to assign "PV" for external SCM

On Mon, 22 Jun 2026, Paul Barker wrote:

> On Mon, 2026-06-22 at 05:08 -0400, Robert P. J. Day wrote:
> > In addition to hard-coding a PV value in the context of an external
> > SCM, show also the alternative of simply appending the string "+git"
> > to the value already calculated for PV from the recipe file name.
> >
> > Signed-off-by: Robert P. J. Day <[email protected]>
> >
> > ---
> >
> > diff --git a/documentation/dev-manual/external-scm.rst b/documentation/dev-manual/external-scm.rst
> > index e7ab8a4c6..adab4370f 100644
> > --- a/documentation/dev-manual/external-scm.rst
> > +++ b/documentation/dev-manual/external-scm.rst
> > @@ -13,9 +13,17 @@ 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::
> > +You can do this in one of two ways:
> >
> > -   PV = "1.2.3+git"
> > +-  Manually assign a version number and the string "+git"
> > +   in the recipe::
> > +
> > +      PV = "1.2.3+git"
> > +
> > +-  A more elegant way is to simply append the "+git" string to the
> > +   value of :term:`PV` already extracted from the recipe file name::
> > +
> > +      PV .= "+git"
> >
> >  :term:`Bitbake` later includes the source control information in :term:`PKGV`
> >  during the packaging phase.
>
> Hi Robert,
>
> What's the benefit to offering users two ways to accomplish the same
> thing?
>
> IMHO this makes the docs less easy to follow, rather than more.

  Because both approaches are used in the code base, and if you're
going to explain how to do something, it's helpful to point to
examples in the code base.

rday