Re: [docs] [PATCH] dev-manual: clarify use of "PACKAGE_ARCH" in a packagegroup

On Tue, 16 Jun 2026, Antonin Godard wrote:

> Hi,
>
> On Tue Jun 16, 2026 at 3:17 PM CEST, Robert P. J. Day wrote:
> >
> > Warn the developer that if they need to set "PACKAGE_ARCH" in a
> > custom packagegroup file, that setting must precede the "inherit
> > packagegroup" line in the packagegroup recipe file.
> >
> > Signed-off-by: Robert P. J. Day <[email protected]>
> >
> > ---
> >
> > diff --git a/documentation/dev-manual/customizing-images.rst b/documentation/dev-manual/customizing-images.rst
> > index 6eed9ef56..606252fe1 100644
> > --- a/documentation/dev-manual/customizing-images.rst
> > +++ b/documentation/dev-manual/customizing-images.rst
> > @@ -183,6 +183,18 @@ build an image using these package group packages, you need to add
> >  :term:`IMAGE_INSTALL`. For other forms of image dependencies see the other
> >  areas of this section.
> >
> > +.. note::
> > +
> > +   If you're defining a packagegroup and need to set::
> > +
> > +      PACKAGE_ARCH = "${MACHINE_ARCH}"
> > +
> > +   for the packagegroup, you need to do that *before* the
> > +   ``inherit packagegroup`` line in the recipe file.
> > +   Setting it afterward can break BitBake parsing, result in
> > +   an "allarch" architecture mismatch error, or allow
> > +   architecture-independent defaults to override your intent.
> > +
> >  Customizing an Image Hostname
> >  =============================
>
> Again, I think this belongs to the packagegroup class documentation.

  ah, the "class" documentation.  got it.

rday