diff mbox series

[46/53] ref-manual/faq.rst: remove obsolete poky repo references

Message ID 20251224-remove-poky-references-v1-46-658a5f4dbde2@bootlin.com
State New
Headers show
Series Remove obsolete poky repo references | expand

Commit Message

Antonin Godard Dec. 24, 2025, 4:32 p.m. UTC
Refresh the document now that the Poky repository is obsolete.

Rework the difference between Poky and OpenEmbedded. Copy the note from
terms.rst regarding the now obsolete Poky repository.

Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
---
 documentation/ref-manual/faq.rst | 43 ++++++++++++++++++++++++++++++----------
 1 file changed, 32 insertions(+), 11 deletions(-)
diff mbox series

Patch

diff --git a/documentation/ref-manual/faq.rst b/documentation/ref-manual/faq.rst
index 406b2c388..cd4801baa 100644
--- a/documentation/ref-manual/faq.rst
+++ b/documentation/ref-manual/faq.rst
@@ -12,14 +12,35 @@  General questions
 How does Poky differ from OpenEmbedded?
 ---------------------------------------
 
-The term ``Poky`` refers to the specific reference build
-system that the Yocto Project provides. Poky is based on
-:term:`OpenEmbedded-Core (OE-Core)` and :term:`BitBake`. Thus, the
-generic term used here for the build system is the "OpenEmbedded build
-system." Development in the Yocto Project using Poky is closely tied to
-OpenEmbedded, with changes always being merged to OE-Core or BitBake
-first before being pulled back into Poky. This practice benefits both
-projects immediately.
+The term :term:`Poky` refers to the reference distribution that the Yocto
+Project provides, and a reference test configuration.
+
+The :term:`Poky` distribution is built using the :term:`OpenEmbedded Build
+System` and :term:`BitBake`. The :term:`metadata` used involved to build the
+:term:`Poky` reference distribution is:
+
+-  :term:`OpenEmbedded-Core (OE-Core)`, which is hosted at
+   :oe_git:`/openembedded-core`.
+
+-  :yocto_git:`meta-poky <meta-yocto/tree/meta-poky>`, which defines the
+   ``poky`` distro configuration file (:term:`DISTRO`).
+
+.. note::
+
+   Poky also used to be a repository containing the combination of
+   :term:`BitBake`, :term:`OpenEmbedded-Core (OE-Core)`, the
+   :yocto_git:`meta-yocto </meta-yocto>` repository and the Yocto Project
+   documentation -- which were combined with the :yocto_git:`combo-layer
+   </poky-config>` tool.
+
+   This repository is still hosted at :yocto_git:`/poky` and is still
+   updated for maintained releases that are older than Whinlatter (5.3).
+   Newer releases now use ``bitbake-setup`` to clone and setup the initial
+   :term:`OpenEmbedded Build System` environment. For more information on
+   how to use ``bitbake-setup``, see the :doc:`/brief-yoctoprojectqs/index`
+   document. An alternative can be to setup the above repositories
+   manually, by following the :doc:`/dev-manual/poky-manual-setup`
+   section of the Yocto Project Development Tasks Manual.
 
 How can you claim Poky / OpenEmbedded-Core is stable?
 -----------------------------------------------------
@@ -27,7 +48,7 @@  How can you claim Poky / OpenEmbedded-Core is stable?
 There are three areas that help with stability;
 
 -  The Yocto Project team keeps :term:`OpenEmbedded-Core (OE-Core)` small and
-   focused, containing around 830 recipes as opposed to the thousands
+   focused, containing around a thousand recipes as opposed to the thousands
    available in other OpenEmbedded community layers. Keeping it small
    makes it easy to test and maintain.
 
@@ -87,8 +108,8 @@  configurable. You can setup the build system to get source code in most
 environments if HTTP transport is available.
 
 When the build system searches for source code, it first tries the local
-download directory. If that location fails, Poky tries
-:term:`PREMIRRORS`, the upstream source, and then
+download directory. If that location fails, the :term:`OpenEmbedded Build
+System` tries :term:`PREMIRRORS`, the upstream source, and then
 :term:`MIRRORS` in that order.
 
 Assuming your distribution is "poky", the OpenEmbedded build system uses