diff mbox series

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

Message ID f94df486-b32b-d301-fc6b-b1a5d560298a@crashcourse.ca
State Superseded
Headers show
Series overview-manual/yp-intro.rst: update on-target packaging info | expand

Commit Message

Robert P. J. Day Oct. 24, 2025, 10:58 a.m. UTC
- drop references to obsolete tar packaging format
  - add reference to on-target "apt" utility for .deb packaging

Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>

---

Comments

Quentin Schulz Oct. 24, 2025, 11:15 a.m. UTC | #1
Hi Robert,

On 10/24/25 12:55 PM, Robert P. J. Day via lists.yoctoproject.org wrote:
> 
>    - drop references to obsolete tar packaging format
>    - add reference to on-target "apt" utility for .deb packaging
> 
> Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
> 
> ---
> 
> diff --git a/documentation/overview-manual/yp-intro.rst b/documentation/overview-manual/yp-intro.rst
> index 8fa17b191..ed50aff93 100644
> --- a/documentation/overview-manual/yp-intro.rst
> +++ b/documentation/overview-manual/yp-intro.rst
> @@ -174,11 +174,11 @@ Here are challenges you might encounter when developing using the Yocto Project:
>      changes on the development system within the BitBake environment and
>      then deploying only the updated packages to the target.
> 
> -   The Yocto Project :term:`OpenEmbedded Build System`
> -   produces packages
> -   in standard formats (i.e. RPM, DEB, IPK, and TAR). You can deploy
> -   these packages into the running system on the target by using
> -   utilities on the target such as ``rpm`` or ``ipk``.
> +   The Yocto Project :term:`OpenEmbedded Build System` produces packages
> +   in standard formats (i.e. RPM, DEB and/or IPK). If you included the
> +   "package management" feature in your image, you can deploy

The feature is technically called package-management (with a dash). The 
use of quotes imply (to me) that this is the name of the feature to 
select in YP/OE-Core but that's not the case. When not used to refer to 
the exact string to be put in IMAGE_FEATURES, we currently do not use 
the quotes (and sometimes also add runtime as first word). SO pick one 
or the other?

> +   these packages into the running system on the target by using the
> +   corresponding utilities on the target such as ``rpm``, ``apt`` or ``opkg``.
> 

The tools seem to be dpkg+apt for deb, rpm+dnf for rpm and opkg for ipk, 
c.f. ROOTFS_PKGMANAGE variable. But I guess since we use "such as" in 
the sentence we don't expect to least every possible package manager.

Looks good to me otherwise,

Thanks!
Quentin
Robert P. J. Day Oct. 24, 2025, 11:24 a.m. UTC | #2
On Fri, 24 Oct 2025, Quentin Schulz wrote:

> Hi Robert,
>
> On 10/24/25 12:55 PM, Robert P. J. Day via lists.yoctoproject.org wrote:
> >
> >    - drop references to obsolete tar packaging format
> >    - add reference to on-target "apt" utility for .deb packaging
> >
> > Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
> >
> > ---
> >
> > diff --git a/documentation/overview-manual/yp-intro.rst
> > b/documentation/overview-manual/yp-intro.rst
> > index 8fa17b191..ed50aff93 100644
> > --- a/documentation/overview-manual/yp-intro.rst
> > +++ b/documentation/overview-manual/yp-intro.rst
> > @@ -174,11 +174,11 @@ Here are challenges you might encounter when
> > developing using the Yocto Project:
> >      changes on the development system within the BitBake environment and
> >      then deploying only the updated packages to the target.
> >
> > -   The Yocto Project :term:`OpenEmbedded Build System`
> > -   produces packages
> > -   in standard formats (i.e. RPM, DEB, IPK, and TAR). You can deploy
> > -   these packages into the running system on the target by using
> > -   utilities on the target such as ``rpm`` or ``ipk``.
> > +   The Yocto Project :term:`OpenEmbedded Build System` produces packages
> > +   in standard formats (i.e. RPM, DEB and/or IPK). If you included the
> > +   "package management" feature in your image, you can deploy
>
> The feature is technically called package-management (with a dash). The use of
> quotes imply (to me) that this is the name of the feature to select in
> YP/OE-Core but that's not the case. When not used to refer to the exact string
> to be put in IMAGE_FEATURES, we currently do not use the quotes (and sometimes
> also add runtime as first word). SO pick one or the other?

  i was actually grappling with that very decision -- i knew about the
hyphen, chose not to include it. i'll clean it up.
>
> > +   these packages into the running system on the target by using the
> > +   corresponding utilities on the target such as ``rpm``, ``apt`` or
> > ``opkg``.
> >
>
> The tools seem to be dpkg+apt for deb, rpm+dnf for rpm and opkg for ipk, c.f.
> ROOTFS_PKGMANAGE variable. But I guess since we use "such as" in the sentence
> we don't expect to least every possible package manager.

  i was also pondering how best to phrase that as well, will clean it
up.

rday
diff mbox series

Patch

diff --git a/documentation/overview-manual/yp-intro.rst b/documentation/overview-manual/yp-intro.rst
index 8fa17b191..ed50aff93 100644
--- a/documentation/overview-manual/yp-intro.rst
+++ b/documentation/overview-manual/yp-intro.rst
@@ -174,11 +174,11 @@  Here are challenges you might encounter when developing using the Yocto Project:
    changes on the development system within the BitBake environment and
    then deploying only the updated packages to the target.

-   The Yocto Project :term:`OpenEmbedded Build System`
-   produces packages
-   in standard formats (i.e. RPM, DEB, IPK, and TAR). You can deploy
-   these packages into the running system on the target by using
-   utilities on the target such as ``rpm`` or ``ipk``.
+   The Yocto Project :term:`OpenEmbedded Build System` produces packages
+   in standard formats (i.e. RPM, DEB and/or IPK). If you included the
+   "package management" feature in your image, you can deploy
+   these packages into the running system on the target by using the
+   corresponding utilities on the target such as ``rpm``, ``apt`` or ``opkg``.

 -  *Initial Build Times Can be Significant:* Long initial build times
    are unfortunately unavoidable due to the large number of packages