linux/poky.git/documentation/dev-manual, branch kirkstone

dev-manual/packages.rst: fix example recipe version

2026-02-12T17:00:21+00:00

The example recipe taken above is hello-world on version 1.0 (because PV equals "1.0+git". Fix this issue. (From yocto-docs rev: a48ab61034d50be1026b939112f4a5c58bed7b88) Signed-off-by: Antonin Godard (cherry picked from commit 411122812ced4ec32127a823896a73aacf6eb97c) Signed-off-by: Antonin Godard Signed-off-by: Richard Purdie

dev-manual/packages.rst: rename r0.0 to r0 when PR server is not enabled

2026-02-12T17:00:21+00:00

When we don't have a PR server enabled, we don't have leading ".0" to the PKGR variable, as this is added by the PR server. (From yocto-docs rev: 4c64db73fa68b6dbc11fe4b64452b0d6b7ee0280) Signed-off-by: Antonin Godard (cherry picked from commit 7a0324b6a10e64ee250945747db10ca88040b1ce) Signed-off-by: Antonin Godard Signed-off-by: Richard Purdie

dev-manual/packages.rst: pr server: fix and explain why r0.X increments on SRCREV change

2026-02-12T17:00:21+00:00

The current example of the SRCREV change triggering a gitX bump is wrong, as both gitX and r0.X get incremented. Why this is happening is explained in bug 15729, which I copy here: > +gitX+ is indeed related to changes in the source code. > > r0.X is bumped each time the checksum of the do_package task of the > simple-hello-world-git recipe changes. This happens here: > https://git.openembedded.org/openembedded-core/tree/meta/classes-global/package.bbclass?id=235e6d49e5888ad04416219e10b6df91a738661a#n306 > > This line sets the value of PRAUTO and represents the number X found in > r0.X. It will in the end make it into EXTENDPRAUTO, which itself makes > to PKGR == r0.X. > > This line calls getPR(version, pkgarch, checksum). Between test case 5 > and 6, only the checksum changes. This checksum is the checksum of the > do_package task (gotten from get_do_package_hash() above). > > Now, let's dump what changed with regards to this task between two > consecutive runs, using the sigdata file in build/tmp/stamps/: > > ``` > [...] > Variable fetcher_hashes_dummyfunc value changed from '2650ad6714c3f3248abfe9d3daf1196f307ed494' to '4af682a50174f5deb0397847da97d7cdba4ad067' > ``` > > The last line shows that the value of fetcher_hashes_dummyfunc changed > from '2650ad6714c3f3248abfe9d3daf1196f307ed494' to > '4af682a50174f5deb0397847da97d7cdba4ad067'. Those are the commit hashes > in the git history of the simple-hello-world-git repository. > > Now you can see why this 0.X gets bumped, is because of the SRCREV change. Fix the example, and detail what gets changed and why. [YOCTO #15729] Cc: Robert Berger (From yocto-docs rev: 8d7b549d095c2ca04d4c7ff5a92f6de9fceb8496) Signed-off-by: Antonin Godard (cherry picked from commit 09f0430bc69024b9854c31ba6783ddd807aa4f19) Signed-off-by: Antonin Godard Signed-off-by: Richard Purdie

Add a new "Security" section

2026-01-26T18:54:18+00:00

The current security-related documentation is a bit hard to find and hidden within the development manual. However these are processes that are not part of a development task but is rather a vulnerability reporting process. Create a new "Security" section in the documentation to gather this information. This will be directly visible in the sidebar when opening the documentation. Split the previous security-subjects.rst document into 2 documents: - security-team.rst: defines the roles of the security teams and its members. - reporting-vulnerabilities.rst: guide to report vulnerabilities to the security team. The plan is to backport these documents to active releases. As a consequence, this section should be free of instructions and information that only make sense for a specific release. It should _not_ contain documents on how to enable security features with Yocto on target devices, this is unrelated and can be left in the development manual (for example: dev-manual/vulnerabilities.rst to deal with CVEs). (From yocto-docs rev: 3fd0f37d708d88534dd6dbb51dc264911c349352) Signed-off-by: Antonin Godard (cherry picked from commit 81e14ca2d5cff9e2104c556655144b069633790c) Signed-off-by: Antonin Godard Signed-off-by: Richard Purdie

documentation: link to the Releases page on yoctoproject.org instead of wiki

2025-11-19T16:21:24+00:00

We have a machine-generated Releases page[1] which is preferable to the wiki. [1] https://www.yoctoproject.org/development/releases/ (From yocto-docs rev: 492619059cbbe2d1ebc347c3e86072f32d7d064a) Signed-off-by: Ross Burton Signed-off-by: Antonin Godard (cherry picked from commit 46a9172fd17aa518028e35b8c874e74889079094) Signed-off-by: Antonin Godard Signed-off-by: Steve Sakoman

dev-manual: debugging: use bitbake-getvar in Viewing Variable Values section

2025-11-19T16:21:24+00:00

We should recommend using bitbake-getvar command wherever possible as its output is much less confusing and overwhelming than bitbake -e. Unfortunately, bitbake-getvar currently doesn't list Python tasks or functions, unlike bitbake -e, so keep the latter for some corner cases. [AG: Moroever -> Moreover typo fix] (From yocto-docs rev: 382c8eee275eb4773d4e2183f5fe19837a6a3b0b) Signed-off-by: Quentin Schulz Signed-off-by: Antonin Godard (cherry picked from commit 41e4e05369c4e028c679749b7b62434327927a09) Signed-off-by: Antonin Godard Signed-off-by: Steve Sakoman

dev-manual/new-recipe.rst: typo, "whith" -> "which"

2025-11-19T16:21:24+00:00

Fix typo "whith", should be "which". (From yocto-docs rev: 1a54d05d8bd5484e17cbc060fc57fd2f7afb683f) Signed-off-by: Robert P. J. Day Signed-off-by: Antonin Godard (cherry picked from commit f98b25f7f7522cf223beb001cabef870d6dd8c10) Signed-off-by: Antonin Godard Signed-off-by: Steve Sakoman

dev-manual/new-recipe.rst: replace 'bitbake -e' with 'bitbake-getvar'

2025-11-19T16:21:24+00:00

Replace the legacy call to 'bitbake -e' to get the value of a recipe's variable with the newer call to 'bitbake-getvar'. (From yocto-docs rev: d7ef362307daf2e8d9b62ec895e080654abfef8b) Signed-off-by: Robert P. J. Day Reviewed-by: Quentin Schulz Signed-off-by: Antonin Godard (cherry picked from commit ed7c0766ef5f13b90943a69e64f8e8713d05e864) Signed-off-by: Antonin Godard Signed-off-by: Steve Sakoman

dev-manual/layers.rst: document "bitbake-layers show-machines"

2025-11-19T16:21:24+00:00

The "show-machines" subcommand is not mentioned in the docs; add it. [AG: fix conflicts] (From yocto-docs rev: 09bbdc6bc5f9ae77f120185d1324f1166ac1f9d5) Signed-off-by: Robert P. J. Day Signed-off-by: Antonin Godard (cherry picked from commit b4320cdc4df08c59a24d5247b3895dd602554fa0) Signed-off-by: Antonin Godard Signed-off-by: Steve Sakoman

dev-manual/new-recipe.rst: update "recipetool -h" output

2025-11-19T16:21:24+00:00

Update the output of "recipetool -h" to include the missing "edit" subcommand. (From yocto-docs rev: 2a85eab0c51a78ab00168e23274d479cf3aedb24) Signed-off-by: Robert P. J. Day Signed-off-by: Antonin Godard (cherry picked from commit 092d688349b0b6bb10ae6fbbab7d82801964daf5) Signed-off-by: Antonin Godard Signed-off-by: Steve Sakoman