dev-manual: CH 2, small number of clarifications

- drop reference to "opkg", just refer in general to packagers
  - correct what "QEMU" stands for (missing space)
  - correct version conditional
  - add a couple extra steps to typical workflow
  - drop implication that one can modify local poky checkout

(From yocto-docs rev: 4fea81e42c41fc42548dd9e2b42f836daba5ac6b)

Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Robert P. J. Day 2025-06-20 06:28:46 -04:00 committed by Richard Purdie
parent d06769ae03
commit 06595cf590

View File

@ -109,7 +109,7 @@ particular working environment and set of practices.
- Keep your cross-development toolchains updated. You can do this - Keep your cross-development toolchains updated. You can do this
through provisioning either as new toolchain downloads or as through provisioning either as new toolchain downloads or as
updates through a package update mechanism using ``opkg`` to updates through a package update mechanism to
provide updates to an existing toolchain. The exact mechanics of provide updates to an existing toolchain. The exact mechanics of
how and when to do this depend on local policy. how and when to do this depend on local policy.
@ -159,7 +159,7 @@ particular working environment and set of practices.
are made. are made.
- Allows triggering of automated image booting and testing under - Allows triggering of automated image booting and testing under
the QuickEMUlator (QEMU). the Quick EMUlator (QEMU).
- Supports incremental build testing and from-scratch builds. - Supports incremental build testing and from-scratch builds.
@ -310,7 +310,7 @@ Project Build Host:
- GNU make &MIN_MAKE_VERSION; or greater - GNU make &MIN_MAKE_VERSION; or greater
If your build host does not meet any of these listed version If your build host does not satisfy all of these listed version
requirements, you can take steps to prepare the system so that you requirements, you can take steps to prepare the system so that you
can still use the Yocto Project. See the can still use the Yocto Project. See the
":ref:`ref-manual/system-requirements:required git, tar, python, make and gcc versions`" ":ref:`ref-manual/system-requirements:required git, tar, python, make and gcc versions`"
@ -568,7 +568,7 @@ extension accordingly.
Locating Yocto Project Source Files Locating Yocto Project Source Files
=================================== ===================================
This section shows you how to locate, fetch and configure the source This section shows you how to locate, fetch, unpack, patch and configure the source
files you'll need to work with the Yocto Project. files you'll need to work with the Yocto Project.
.. note:: .. note::
@ -720,11 +720,11 @@ Follow these steps to create a local version of the upstream
$ git branch $ git branch
* master * master
Your local repository of poky is identical to the Your local repository of poky is initially identical to the
upstream poky repository at the time from which it was cloned. As you upstream poky repository from which it was cloned. As you
work with the local branch, you can periodically use the work with the local branch, you can periodically use the
``git pull --rebase`` command to be sure you are up-to-date ``git pull`` command to be sure you stay up-to-date
with the upstream branch. with the upstream poky branch.
Checking Out by Branch in Poky Checking Out by Branch in Poky
------------------------------ ------------------------------