mbox series

[v3,0/4] propagate distro-specific dependencies of arch all packages

Message ID 20251106141122.2887558-1-felix.moessbauer@siemens.com
Headers show
Series propagate distro-specific dependencies of arch all packages | expand

Message

MOESSBAUER, Felix Nov. 6, 2025, 2:11 p.m. UTC 
Changes since v2:

Fix root cause of linux-module build errors on cross:
The previous linux-custom recipe used the cross profile also to control
which packages are built in a cross setting, which is fundamentally wrong.
We now split this custom profile off the official one and attach it to the
cross-profile logic of linux-custom (which refers to "we are in a
HOST_ARCH != DISTRO_ARCH setting" instead of we are cross-compiling this
package). The cleanup is done in two stages: First, we properly prefix
all used custom build profiles according to the build profile spec (p1),
second we split off the cross profile (p2).

@Stefan: It would be great if you could test this series on your original
use case.

Best regards,
Felix

Felix Moessbauer (2):
  linux-custom: prefix profile names according to BuildProfileSpec
  linux-custom: fix name collision on cross profile
  do not add cross profile when building native package
  propagate distro-specific dependencies of arch all packages

 meta/classes/dpkg-base.bbclass                |  2 +-
 meta/classes/multiarch.bbclass                | 10 ++++---
 .../linux/files/debian/control.tmpl           | 16 +++++------
 .../linux/files/debian/isar/install.tmpl      |  2 +-
 meta/recipes-kernel/linux/linux-custom.inc    | 27 ++++++++++++-------
 5 files changed, 33 insertions(+), 24 deletions(-)

Comments

Zhihang Wei Nov. 7, 2025, 10:09 a.m. UTC | #1 
v3 LGTM and passed CI.

On 11/6/25 15:11, 'Felix Moessbauer' via isar-users wrote:
> Changes since v2:
>
> Fix root cause of linux-module build errors on cross:
> The previous linux-custom recipe used the cross profile also to control
> which packages are built in a cross setting, which is fundamentally wrong.
> We now split this custom profile off the official one and attach it to the
> cross-profile logic of linux-custom (which refers to "we are in a
> HOST_ARCH != DISTRO_ARCH setting" instead of we are cross-compiling this
> package). The cleanup is done in two stages: First, we properly prefix
> all used custom build profiles according to the build profile spec (p1),
> second we split off the cross profile (p2).
>
> @Stefan: It would be great if you could test this series on your original
> use case.
>
> Best regards,
> Felix
>
> Felix Moessbauer (2):
>    linux-custom: prefix profile names according to BuildProfileSpec
>    linux-custom: fix name collision on cross profile
>    do not add cross profile when building native package
>    propagate distro-specific dependencies of arch all packages
>
>   meta/classes/dpkg-base.bbclass                |  2 +-
>   meta/classes/multiarch.bbclass                | 10 ++++---
>   .../linux/files/debian/control.tmpl           | 16 +++++------
>   .../linux/files/debian/isar/install.tmpl      |  2 +-
>   meta/recipes-kernel/linux/linux-custom.inc    | 27 ++++++++++++-------
>   5 files changed, 33 insertions(+), 24 deletions(-)
>
MOESSBAUER, Felix Nov. 7, 2025, 10:20 a.m. UTC | #2 
On Fri, 2025-11-07 at 11:09 +0100, Zhihang Wei wrote:
> v3 LGTM and passed CI.

Many thanks for the patience and guidance. Once integrated, we finally
can move forward with the SBOM series.

Best regards,
Felix

> 
> On 11/6/25 15:11, 'Felix Moessbauer' via isar-users wrote:
> > Changes since v2:
> > 
> > Fix root cause of linux-module build errors on cross:
> > The previous linux-custom recipe used the cross profile also to control
> > which packages are built in a cross setting, which is fundamentally wrong.
> > We now split this custom profile off the official one and attach it to the
> > cross-profile logic of linux-custom (which refers to "we are in a
> > HOST_ARCH != DISTRO_ARCH setting" instead of we are cross-compiling this
> > package). The cleanup is done in two stages: First, we properly prefix
> > all used custom build profiles according to the build profile spec (p1),
> > second we split off the cross profile (p2).
> > 
> > @Stefan: It would be great if you could test this series on your original
> > use case.
> > 
> > Best regards,
> > Felix
> > 
> > Felix Moessbauer (2):
> >    linux-custom: prefix profile names according to BuildProfileSpec
> >    linux-custom: fix name collision on cross profile
> >    do not add cross profile when building native package
> >    propagate distro-specific dependencies of arch all packages
> > 
> >   meta/classes/dpkg-base.bbclass                |  2 +-
> >   meta/classes/multiarch.bbclass                | 10 ++++---
> >   .../linux/files/debian/control.tmpl           | 16 +++++------
> >   .../linux/files/debian/isar/install.tmpl      |  2 +-
> >   meta/recipes-kernel/linux/linux-custom.inc    | 27 ++++++++++++-------
> >   5 files changed, 33 insertions(+), 24 deletions(-)
> >