From 0c33a64edda790b35ff8288c288648214ab09f9f Mon Sep 17 00:00:00 2001 From: Michael Opdenacker Date: Tue, 12 Sep 2023 10:32:22 +0200 Subject: 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: b51c21e59bd624153f6f9b8bf3cf33329bd25e56) Signed-off-by: Michael Opdenacker Signed-off-by: Richard Purdie --- documentation/dev-manual/new-recipe.rst | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) (limited to 'documentation/dev-manual') diff --git a/documentation/dev-manual/new-recipe.rst b/documentation/dev-manual/new-recipe.rst index cb9533ff5d..457f9632ce 100644 --- a/documentation/dev-manual/new-recipe.rst +++ b/documentation/dev-manual/new-recipe.rst @@ -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 ========================= -- cgit v1.2.3-54-g00ecf