mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-05-30 12:29:55 +00:00
Code Issues Projects Releases Wiki Activity

contributor-guide/style-guide: Refer to recipes, not packages

Browse Source 
Whilst often referred to as packages by people we should use the more
accurate term in documentation, 'recipe' instead of 'packages'.

(From yocto-docs rev: 058de5ad48ab76c4d54391f1701c3082842e8794)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Richard Purdie
2023-09-20 15:52:08 +01:00
parent 5614e6b38a
commit 3eb4532cad
1 changed files with 8 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/contributor-guide/recipe-style-guide.rst
+8 -7
View File
@@ -7,17 +7,18 @@ Recipe Naming Conventions
========================= =========================
In general, most recipes should follow the naming convention In general, most recipes should follow the naming convention
``recipes-category/package/packagename_version.bb``. Recipes for related ``recipes-category/recipename/recipename_version.bb``. Recipes for related
projects may share the same package directory. ``packagename``, ``category``, projects may share the same recipe directory. ``recipename`` and ``category``
and ``package`` may contain hyphens, but hyphens are not allowed in ``version``. may contain hyphens, but hyphens are not allowed in ``version``.
If the recipe is tracking a Git revision that does not correspond to a released If the recipe is tracking a Git revision that does not correspond to a released
version of the software, ``version`` may be ``git`` (e.g. ``packagename_git.bb``) version of the software, ``version`` may be ``git`` (e.g. ``recipename_git.bb``)
and the recipe would set :term:`PV`.
Version Policy Version Policy
============== ==============
Our versions follow the form ``<package epoch>:<package version>-<package revision>`` Our versions follow the form ``<epoch>:<version>-<revision>``
or in BitBake variable terms ${:term:`PE`}:${:term:`PV`}-${:term:`PR`}. We or in BitBake variable terms ${:term:`PE`}:${:term:`PV`}-${:term:`PR`}. We
generally follow the `Debian <https://www.debian.org/doc/debian-policy/ch-controlfields.html#version>`__ generally follow the `Debian <https://www.debian.org/doc/debian-policy/ch-controlfields.html#version>`__
version policy which defines these terms. version policy which defines these terms.
@@ -26,7 +27,7 @@ In most cases the version :term:`PV` will be set automatically from the recipe
file name. It is recommended to use released versions of software as these are file name. It is recommended to use released versions of software as these are
revisions that upstream are expecting people to use. revisions that upstream are expecting people to use.
Package versions should always compare and sort correctly so that upgrades work Recipe versions should always compare and sort correctly so that upgrades work
as expected. With conventional versions such as ``1.4`` upgrading ``to 1.5`` as expected. With conventional versions such as ``1.4`` upgrading ``to 1.5``
this happens naturally, but some versions don't sort. For example, this happens naturally, but some versions don't sort. For example,
``1.5 Release Candidate 2`` could be written as ``1.5rc2`` but this sorts after ``1.5 Release Candidate 2`` could be written as ``1.5rc2`` but this sorts after
@@ -62,7 +63,7 @@ Version Number Changes
The :term:`PR` variable is used to indicate different revisions of a recipe The :term:`PR` variable is used to indicate different revisions of a recipe
that reference the same upstream source version. It can be used to force a that reference the same upstream source version. It can be used to force a
new version of a package to be installed onto a device from a package feed. new version of a recipe to be installed onto a device from a package feed.
These once had to be set manually but in most cases these can now be set and These once had to be set manually but in most cases these can now be set and
incremented automatically by a PR Server connected with a package feed. incremented automatically by a PR Server connected with a package feed.