On Mon, Jul 06, 2026 at 10:52:48AM +0100, Paul Barker wrote: > On Fri, 2026-07-03 at 17:29 +0300, Leon Anavi via lists.openembedded.org > wrote: > > Add pam to the list of DISTRO_FEATURES_DEFAULTS if variable > > VIRTUAL-RUNTIME_init_manager has been set to systemd. Otherwise > > having systemd in conjunction with wayland but without pam leads > > to a conflict with the REQUIRED_DISTRO_FEATURES for weston related > > recipes. > > > > This adjustment is required following these recent changes that > > switched VIRTUAL-RUNTIME_init_manager to systemd by default and added > > wayland to DISTRO_FEATURES_DEFAULTS which affects "nodistro": > > > > - 159148f4de2595556fef6e8678578df83383857b > > meta: Support opting out of any distro features > > (Please note that this commit also extended DISTRO_FEATURES_DEFAULTS > > with wayland and vulkan.) > > > > - 0b4061c5d50261f826d0edb4b478d2d305274b7c > > conf: Switch to systemd by default and simplify init manager selection > > > > This fixes issues with test_machine_world when running the > > yocto-check-layer script for BSP layers that include weston in the > > dependency chain, for example meta-tegra: > > > > ERROR: Required build target 'meta-world-pkgdata' has no buildable > > providers. > > Missing or unbuildable dependency chain was: ['meta-world-pkgdata', > > 'l4t-graphics-demos', 'weston'] > > > > The weston recipe has pam in REQUIRED_DISTRO_FEATURES if systemd is > > enabled. Therefore, it makes sense to also add pam to the defaults > > through DISTRO_FEATURES_DEFAULTS. > > > > Signed-off-by: Leon Anavi <[email protected]> > > --- > > meta/conf/distro/include/default-distrovars.inc | 1 + > > 1 file changed, 1 insertion(+) > > > > diff --git a/meta/conf/distro/include/default-distrovars.inc > > b/meta/conf/distro/include/default-distrovars.inc > > index 69c6db589b..2eadfcbd74 100644 > > --- a/meta/conf/distro/include/default-distrovars.inc > > +++ b/meta/conf/distro/include/default-distrovars.inc > > @@ -29,6 +29,7 @@ DISTRO_FEATURES_DEFAULTS ?= " \ > > acl alsa bluetooth debuginfod ext2 ipv4 ipv6 \ > > wifi xattr nfs zeroconf pci 3g nfc x11 vfat seccomp pulseaudio \ > > gobject-introspection-data ldconfig opengl ptest multiarch wayland > > vulkan \ > > + ${@oe.utils.conditional('VIRTUAL-RUNTIME_init_manager', 'systemd', > > 'pam', '', d)} \ > > " > > IMAGE_FEATURES ?= "" > > Hi Leon, > > I'm not sure we want to enable pam for everyone using systemd, there may > be many systemd users who don't use weston. > > If we do want to enable pam whenever systemd is in use, the better place > to do it is in meta/conf/distro/include/init-manager-systemd.inc. > > An alternative, though not the most satisfying, may be to add a > REQUIRED_DISTRO_FEATURES check to the l4t-graphics-demos recipe in > meta-tegra.
Hey Paul, So, it's certainly an interesting part of making a layer be yocto-check-layer compatible. Related to what I believe Leon mentioned elsewhere, there's a lot of unsatisfying changes one needs to make to the metadata in order to pass the signature check part of the script. So please do let us know if the right answer here, for yocto-check-layer compatibility is to instead add a check in l4t-graphics-demos to pass the signature test. Thanks! -- Tom
signature.asc
Description: PGP signature
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#240402): https://lists.openembedded.org/g/openembedded-core/message/240402 Mute This Topic: https://lists.openembedded.org/mt/120100403/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
