dev-manual: new-recipe.rst fix inconsistency with contributor guide

This document was suggesting a way to version pre-releases
which doesn't match the latest recommendations from the
contributor guide.

(From yocto-docs rev: f37c9e7d44a2f7aefc3b505ae4461e6f1a8b0bb2)

Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Steve Sakoman <steve@sakoman.com>
This commit is contained in:
Michael Opdenacker
2023-09-12 10:32:22 +02:00
committed by Steve Sakoman
parent 31af34e1af
commit b17bb4e9c0

View File

@@ -1036,13 +1036,14 @@ build system and package managers, so the resulting packages will not
correctly trigger an upgrade.
In order to ensure the versions compare properly, the recommended
convention is to set :term:`PV` within the
recipe to "previous_version+current_version". You can use an additional
variable so that you can use the current version elsewhere. Here is an
example::
convention is to use a tilde (``~``) character as follows::
REALPV = "0.8.16-rc1"
PV = "0.8.15+${REALPV}"
PV = 0.8.16~rc1
This way ``0.8.16~rc1`` sorts before ``0.8.16``. See the
":ref:`contributor-guide/recipe-style-guide:version policy`" section in the
Yocto Project and OpenEmbedded Contributor Guide for more details about
versioning code corresponding to a pre-release or to a specific Git commit.
Post-Installation Scripts
=========================