overview-manual/yp-intro.rst: update on-target packaging info

- drop references to obsolete tar packaging format
  - add references to apt and dpkg utilities for .deb packaging
  - add reference to alternative "dnf" .rpm packaging

(From yocto-docs rev: d1331418317576b569ea2b046adf46ec7af8a15a)

Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
(cherry picked from commit d4374ac86ebe7980908ed905018ccfb773ac666e)
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Steve Sakoman <steve@sakoman.com>
This commit is contained in:
Robert P. J. Day
2025-10-24 07:37:07 -04:00
committed by Steve Sakoman
parent ba0fd17fa6
commit b0e19cc72f

View File

@@ -172,11 +172,12 @@ Here are challenges you might encounter when developing using the Yocto Project:
changes on the development system within the BitBake environment and changes on the development system within the BitBake environment and
then deploying only the updated packages to the target. then deploying only the updated packages to the target.
The Yocto Project :term:`OpenEmbedded Build System` The Yocto Project :term:`OpenEmbedded Build System` produces packages
produces packages in standard formats (i.e. RPM, DEB and/or IPK). If you included the
in standard formats (i.e. RPM, DEB, IPK, and TAR). You can deploy runtime package management feature in your image, you can deploy
these packages into the running system on the target by using these packages into the running system on the target by using the
utilities on the target such as ``rpm`` or ``ipk``. corresponding utilities on the target such as
``rpm``/``dnf``, ``dpkg``/``apt`` or ``opkg``.
- *Initial Build Times Can be Significant:* Long initial build times - *Initial Build Times Can be Significant:* Long initial build times
are unfortunately unavoidable due to the large number of packages are unfortunately unavoidable due to the large number of packages