Skip to contentSkip to conversation

systemd: allow building for nativesdk

PATCH Superseded [email protected] 6 participants 46 messages Nov 17, 2021 – Nov 24, 2021 Arm/Amlogic Meson SoC support

lore
Share & tools
lore
#0 lore raw

cover systemd: allow building for nativesdk

From: Luca Boccassi <[email protected]>

systemd-analyze in the next release will gain the ability to run the 'security' and 'verify' verbs offline, on local units. This is very useful at build time and/or in CI systems to detect errors and issues before changes are deployed, as a static analyzer tool.
This series enables building the systemd recipe for the nativesdk targets, so that systemd-analyze can be included in the SDK and called by users/build systems/CI systems.

Luca Boccassi (8):
systemd: skip chown when building for nativesdk
systemd: skip postinst in nativesdk builds
systemd: remove /var in nativesdk builds
volatile-binds: remove /var in nativesdk builds
volatile-binds: add nativesdk
kbd: add nativesdk
os-release: add nativesdk
systemd: add nativesdk

 meta/recipes-core/kbd/kbd_2.4.0.bb            |  2 +-
 meta/recipes-core/os-release/os-release.bb    |  2 ++
 meta/recipes-core/systemd/systemd-conf_1.0.bb |  2 ++
 .../systemd/systemd-serialgetty.bb            |  2 ++
 meta/recipes-core/systemd/systemd_249.5.bb    | 29 +++++++++++++++++--
 .../volatile-binds/volatile-binds.bb          |  7 +++++
 6 files changed, 41 insertions(+), 3 deletions(-)
Signature · 1 line
2.30.2
#1 lore raw

PATCH 1/8 systemd: skip chown when building for nativesdk

From: Luca Boccassi <[email protected]>

The useradd class is a no-op in the nativesdk case, so chown will fail. Skip them.

---
 meta/recipes-core/systemd/systemd_249.5.bb | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)
meta/recipes-core/systemd/systemd_249.5.bb +8 -2
index 8bdc0ca028..2f019a4b1f 100644
@@ -275,7 +275,10 @@ do_install() {
 		# which is expected to be empty.
 		rm -rf ${D}${localstatedir}/log
 	else
-		chown root:systemd-journal ${D}${localstatedir}/log/journal
+		# The useradd class is a no-op in the nativesdk case, so chown will fail
+		if [ "${PN}" != "nativesdk-systemd" ]; then
+			chown root:systemd-journal ${D}${localstatedir}/log/journal
+		fi
 
 		# journal-remote creates this at start
 		rm -rf ${D}${localstatedir}/log/journal/remote
@@ -319,7 +322,10 @@ do_install() {
 	if ${@bb.utils.contains('PACKAGECONFIG', 'polkit', 'true', 'false', d)}; then
 		if [ -d ${D}${datadir}/polkit-1/rules.d ]; then
 			chmod 700 ${D}${datadir}/polkit-1/rules.d
-			chown polkitd:root ${D}${datadir}/polkit-1/rules.d
+			# The useradd class is a no-op in the nativesdk case, so chown will fail
+			if [ "${PN}" != "nativesdk-systemd" ]; then
+				chown polkitd:root ${D}${datadir}/polkit-1/rules.d
+			fi
 		fi
 	fi
 
Signature · 1 line
2.30.2
#2 lore raw

RE: [OE-core] [PATCH 1/8] systemd: skip chown when building for nativesdk

Quoted 22 lines

-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Luca Bocassi
Sent: den 17 november 2021 13:32
To: [email protected]
Cc: [email protected]
Subject: [OE-core] [PATCH 1/8] systemd: skip chown when building for nativesdk

From: Luca Boccassi <[email protected]>

The useradd class is a no-op in the nativesdk case, so chown will fail. Skip them.

---
 meta/recipes-core/systemd/systemd_249.5.bb | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)
meta/recipes-core/systemd/systemd_249.5.bb +0 -0
index 8bdc0ca028..2f019a4b1f 100644

meta/recipes-core/systemd/systemd_249.5.bb do_install() { · line 279

Quoted 6 lines
meta/recipes-core/systemd/systemd_249.5.bb +2 -1
@@ -275,7 +275,10 @@ do_install() {
 		# which is expected to be empty.
 		rm -rf ${D}${localstatedir}/log
 	else
-		chown root:systemd-journal ${D}${localstatedir}/log/journal
+		# The useradd class is a no-op in the nativesdk case, so chown will fail
+		if [ "${PN}" != "nativesdk-systemd" ]; then

If you change that if statement here and below to:

		if [ "${PN}" = "${BPN}" ]; then

then it will apply just as well if anyone introduces systemd-native.

Quoted 18 lines
meta/recipes-core/systemd/systemd_249.5.bb +6 -2
+			chown root:systemd-journal ${D}${localstatedir}/log/journal
+		fi
 
 		# journal-remote creates this at start
 		rm -rf ${D}${localstatedir}/log/journal/remote
@@ -319,7 +322,10 @@ do_install() {
 	if ${@bb.utils.contains('PACKAGECONFIG', 'polkit', 'true', 'false', d)}; then
 		if [ -d ${D}${datadir}/polkit-1/rules.d ]; then
 			chmod 700 ${D}${datadir}/polkit-1/rules.d
-			chown polkitd:root ${D}${datadir}/polkit-1/rules.d
+			# The useradd class is a no-op in the nativesdk case, so chown will fail
+			if [ "${PN}" != "nativesdk-systemd" ]; then
+				chown polkitd:root ${D}${datadir}/polkit-1/rules.d
+			fi
 		fi
 	fi
 
--
Quoted 1 line

2.30.2

//Peter

#3 lore raw

Re: [OE-core] [PATCH 1/8] systemd: skip chown when building for nativesdk

Quoted 38 lines · Peter Kjellerstedt
Quoted 34 lines

-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Luca Bocassi
Sent: den 17 november 2021 13:32
To: [email protected]
Cc: [email protected]
Subject: [OE-core] [PATCH 1/8] systemd: skip chown when building for nativesdk

From: Luca Boccassi <[email protected]>

The useradd class is a no-op in the nativesdk case, so chown will fail.
Skip them.

---
 meta/recipes-core/systemd/systemd_249.5.bb | 10 ++++++++--

 1 file changed, 8 insertions(+), 2 deletions(-)
meta/recipes-core/systemd/systemd_249.5.bb +0 -0
index 8bdc0ca028..2f019a4b1f 100644
@@ -275,7 +275,10 @@ do_install() {
  		# which is expected to be empty.

  rm -rf ${D}${localstatedir}/log
  else

meta/recipes-core/systemd/systemd_249.5.bb +0 -1
-		chown root:systemd-journal

${D}${localstatedir}/log/journal

meta/recipes-core/systemd/systemd_249.5.bb +1 -0
+		# The useradd class is a no-op in the nativesdk

case, so chown will fail

meta/recipes-core/systemd/systemd_249.5.bb

Quoted 1 line
meta/recipes-core/systemd/systemd_249.5.bb +1 -0
+		if [ "${PN}" != "nativesdk-systemd" ]; then

If you change that if statement here and below to:

Quoted 3 lines
		if [ "${PN}" = "${BPN}" ]; then

then it will apply just as well if anyone introduces systemd-native.

Thanks, will test that and send a v2 tomorrow if it is all green.

Signature · 2 lines
Kind regards,
Luca Boccassi
#4 lore raw

Re: [OE-core] [PATCH 1/8] systemd: skip chown when building for nativesdk

Quoted 39 lines · Luca Boccassi
Quoted 38 lines · Peter Kjellerstedt
Quoted 34 lines

-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Luca Bocassi
Sent: den 17 november 2021 13:32
To: [email protected]
Cc: [email protected]
Subject: [OE-core] [PATCH 1/8] systemd: skip chown when building for nativesdk

From: Luca Boccassi <[email protected]>

The useradd class is a no-op in the nativesdk case, so chown will fail.
Skip them.

---
 meta/recipes-core/systemd/systemd_249.5.bb | 10 ++++++++--

 1 file changed, 8 insertions(+), 2 deletions(-)
meta/recipes-core/systemd/systemd_249.5.bb +0 -0
index 8bdc0ca028..2f019a4b1f 100644
@@ -275,7 +275,10 @@ do_install() {
  		# which is expected to be empty.

  rm -rf ${D}${localstatedir}/log
  else

meta/recipes-core/systemd/systemd_249.5.bb +0 -1
-		chown root:systemd-journal

${D}${localstatedir}/log/journal

meta/recipes-core/systemd/systemd_249.5.bb +1 -0
+		# The useradd class is a no-op in the nativesdk

case, so chown will fail

meta/recipes-core/systemd/systemd_249.5.bb

Quoted 1 line
meta/recipes-core/systemd/systemd_249.5.bb +1 -0
+		if [ "${PN}" != "nativesdk-systemd" ]; then

If you change that if statement here and below to:

Quoted 5 lines
Quoted 3 lines
		if [ "${PN}" = "${BPN}" ]; then

then it will apply just as well if anyone introduces systemd-native.

Thanks, will test that and send a v2 tomorrow if it is all green.

This works, thanks, applied in v2.

Signature · 2 lines
Kind regards,
Luca Boccassi
#5 lore raw

PATCH 2/8 systemd: skip postinst in nativesdk builds

In reply to [email protected]

From: Luca Boccassi <[email protected]>

They will fail, as there's nowhere to run them

---
 meta/recipes-core/systemd/systemd_249.5.bb | 12 ++++++++++++
 1 file changed, 12 insertions(+)
meta/recipes-core/systemd/systemd_249.5.bb +12 -0
index 2f019a4b1f..38a2f5d474 100644
@@ -773,12 +773,18 @@ ALTERNATIVE_LINK_NAME[runlevel] = "${base_sbindir}/runlevel"
 ALTERNATIVE_PRIORITY[runlevel] ?= "300"
 
 pkg_postinst:${PN}:libc-glibc () {
+	if [ "${PN}" = "nativesdk-systemd" ]; then
+		exit 0
+	fi
 	sed -e '/^hosts:/s/\s*\<myhostname\>//' \
 		-e 's/\(^hosts:.*\)\(\<files\>\)\(.*\)\(\<dns\>\)\(.*\)/\1\2 myhostname \3\4\5/' \
 		-i $D${sysconfdir}/nsswitch.conf
 }
 
 pkg_prerm:${PN}:libc-glibc () {
+	if [ "${PN}" = "nativesdk-systemd" ]; then
+		exit 0
+	fi
 	sed -e '/^hosts:/s/\s*\<myhostname\>//' \
 		-e '/^hosts:/s/\s*myhostname//' \
 		-i $D${sysconfdir}/nsswitch.conf
@@ -786,6 +792,9 @@ pkg_prerm:${PN}:libc-glibc () {
 
 PACKAGE_WRITE_DEPS += "qemu-native"
 pkg_postinst:udev-hwdb () {
+	if [ "${PN}" = "nativesdk-systemd" ]; then
+		exit 0
+	fi
 	if test -n "$D"; then
 		$INTERCEPT_DIR/postinst_intercept update_udev_hwdb ${PKG} mlprefix=${MLPREFIX} binprefix=${MLPREFIX} rootlibexecdir="${rootlibexecdir}" PREFERRED_PROVIDER_udev="${PREFERRED_PROVIDER_udev}"
 	else
@@ -794,5 +803,8 @@ pkg_postinst:udev-hwdb () {
 }
 
 pkg_prerm:udev-hwdb () {
+	if [ "${PN}" = "nativesdk-systemd" ]; then
+		exit 0
+	fi
 	rm -f $D${sysconfdir}/udev/hwdb.bin
 }
Signature · 1 line
2.30.2
#6 lore raw

PATCH 3/8 systemd: remove /var in nativesdk builds

In reply to [email protected]

From: Luca Boccassi <[email protected]>

Nothing picks it up, so it fails QA checks

---
 meta/recipes-core/systemd/systemd_249.5.bb | 5 +++++
 1 file changed, 5 insertions(+)
meta/recipes-core/systemd/systemd_249.5.bb +5 -0
index 38a2f5d474..016058cd7f 100644
@@ -772,6 +772,11 @@ ALTERNATIVE_TARGET[runlevel] = "${base_bindir}/systemctl"
 ALTERNATIVE_LINK_NAME[runlevel] = "${base_sbindir}/runlevel"
 ALTERNATIVE_PRIORITY[runlevel] ?= "300"
 
+# Nothing picks up /var in the nativesdk case
+do_install_append_class-nativesdk () {
+	rm -rf ${D}/var
+}
+
 pkg_postinst:${PN}:libc-glibc () {
 	if [ "${PN}" = "nativesdk-systemd" ]; then
 		exit 0
Signature · 1 line
2.30.2
#7 lore raw

PATCH 4/8 volatile-binds: remove /var in nativesdk builds

In reply to [email protected]

From: Luca Boccassi <[email protected]>

Nothing picks it up, so it fails QA checks

---
 meta/recipes-core/volatile-binds/volatile-binds.bb | 5 +++++
 1 file changed, 5 insertions(+)
meta/recipes-core/volatile-binds/volatile-binds.bb +5 -0
index d5c5538cd7..66e28f4fc9 100644
@@ -79,3 +79,8 @@ do_install () {
     ln -s /dev/null ${D}${sysconfdir}/tmpfiles.d/home.conf
 }
 do_install[dirs] = "${WORKDIR}"
+
+# Nothing picks up /var in the nativesdk case
+do_install_append_class-nativesdk () {
+    rm -rf ${D}/var
+}
Signature · 1 line
2.30.2
#8 lore raw

PATCH 5/8 volatile-binds: add nativesdk

In reply to [email protected]

From: Luca Boccassi <[email protected]>

---
 meta/recipes-core/volatile-binds/volatile-binds.bb | 2 ++
 1 file changed, 2 insertions(+)
meta/recipes-core/volatile-binds/volatile-binds.bb +2 -0
index 66e28f4fc9..0f27353031 100644
@@ -84,3 +84,5 @@ do_install[dirs] = "${WORKDIR}"
 do_install_append_class-nativesdk () {
     rm -rf ${D}/var
 }
+
+BBCLASSEXTEND = "nativesdk"
Signature · 1 line
2.30.2
#9 lore raw

Re: [OE-core] [PATCH 5/8] volatile-binds: add nativesdk

Quoted 12 lines · Luca Bocassi

From: Luca Boccassi <[email protected]>

---
 meta/recipes-core/volatile-binds/volatile-binds.bb | 2 ++
 1 file changed, 2 insertions(+)
meta/recipes-core/volatile-binds/volatile-binds.bb +0 -0
index 66e28f4fc9..0f27353031 100644

meta/recipes-core/volatile-binds/volatile-binds.bb do_install[dirs] = "${WORKDIR}" · line 88

Quoted 5 lines
meta/recipes-core/volatile-binds/volatile-binds.bb +2 -0
@@ -84,3 +84,5 @@ do_install[dirs] = "${WORKDIR}"
 do_install_append_class-nativesdk () {
     rm -rf ${D}/var
 }
+
+BBCLASSEXTEND = "nativesdk"

Is there any useful component left in volatile-binds in the SDK case? I don't think we should be extending this as the recipe makes no sense. Rather nativesdk variants probably shouldn't be depending upon it?

Cheers,

Richard

#10 lore raw

Re: [OE-core] [PATCH 5/8] volatile-binds: add nativesdk

Quoted 8 lines · Richard Purdie
Quoted 7 lines · Luca Bocassi

From: Luca Boccassi <[email protected]>

---
 meta/recipes-core/volatile-binds/volatile-binds.bb | 2 ++

 1 file changed, 2 insertions(+)
Quoted 14 lines

meta/recipes-core/volatile-binds/volatile-binds.bb do_install[dirs] = "${WORKDIR}" · line 88

Quoted 10 lines
meta/recipes-core/volatile-binds/volatile-binds.bb +0 -0
index 66e28f4fc9..0f27353031 100644
@@ -84,3 +84,5 @@ do_install[dirs] = "${WORKDIR}"
  do_install_append_class-nativesdk () {

     rm -rf ${D}/var
 }

meta/recipes-core/volatile-binds/volatile-binds.bb +2 -0
+
+BBCLASSEXTEND = "nativesdk"

Is there any useful component left in volatile-binds in the SDK case? I don't think we should be extending this as the recipe makes no sense. Rather nativesdk variants probably shouldn't be depending upon it?

It's pulled in automatically. I don't know enough about yocto to be able to tell whether it's intentional and needed or not.

Signature · 2 lines
Kind regards,
Luca Boccassi
#11 lore raw

Re: [OE-core] [PATCH 5/8] volatile-binds: add nativesdk

Quoted 24 lines · Luca Boccassi
Quoted 8 lines · Richard Purdie
Quoted 7 lines · Luca Bocassi

From: Luca Boccassi <[email protected]>

---
 meta/recipes-core/volatile-binds/volatile-binds.bb | 2 ++

 1 file changed, 2 insertions(+)
Quoted 14 lines

meta/recipes-core/volatile-binds/volatile-binds.bb do_install[dirs] = "${WORKDIR}" · line 88

Quoted 10 lines
meta/recipes-core/volatile-binds/volatile-binds.bb +0 -0
index 66e28f4fc9..0f27353031 100644
@@ -84,3 +84,5 @@ do_install[dirs] = "${WORKDIR}"
  do_install_append_class-nativesdk () {

     rm -rf ${D}/var
 }

meta/recipes-core/volatile-binds/volatile-binds.bb +2 -0
+
+BBCLASSEXTEND = "nativesdk"

Is there any useful component left in volatile-binds in the SDK case? I don't think we should be extending this as the recipe makes no sense. Rather nativesdk variants probably shouldn't be depending upon it?

Quoted 2 lines

It's pulled in automatically. I don't know enough about yocto to be able to tell whether it's intentional and needed or not.

Looks like it's working without, so changed in v2 to remove the dependency for nativesdk instead.

Signature · 2 lines
Kind regards,
Luca Boccassi
#12 lore raw

PATCH 6/8 kbd: add nativesdk

In reply to [email protected]

From: Luca Boccassi <[email protected]>

Required to build systemd tools

---
 meta/recipes-core/kbd/kbd_2.4.0.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
meta/recipes-core/kbd/kbd_2.4.0.bb +1 -1
index 7cb45eff77..7efc7af312 100644
@@ -43,4 +43,4 @@ ALTERNATIVE:${PN} = "chvt deallocvt fgconsole openvt showkey \
                      ${@bb.utils.contains('DISTRO_FEATURES', 'pam', 'vlock','', d)}"
 ALTERNATIVE_PRIORITY = "100"
 
-BBCLASSEXTEND = "native"
+BBCLASSEXTEND = "native nativesdk"
Signature · 1 line
2.30.2
#13 lore raw

Re: [OE-core] [PATCH 6/8] kbd: add nativesdk

Quoted 3 lines · Luca Bocassi

From: Luca Boccassi <[email protected]>

Required to build systemd tools

If systemd needs these to build, wouldn't it be depending on kbd-native?

Or are you saying that systemd-tools needs something in here at runtime?

I don't mind extending the recipe if we really need it but that isn't what the commit message says so at the very least that needs to be clearer.

Cheers,

Richard

#14 lore raw

Re: [OE-core] [PATCH 6/8] kbd: add nativesdk

Quoted 7 lines · Richard Purdie
Quoted 3 lines · Luca Bocassi

From: Luca Boccassi <[email protected]>

Required to build systemd tools

If systemd needs these to build, wouldn't it be depending on kbd-native?

Quoted 9 lines

Or are you saying that systemd-tools needs something in here at runtime?

I don't mind extending the recipe if we really need it but that isn't what the commit message says so at the very least that needs to be clearer.

Cheers,

Richard

It's probably indirect, I guess (dependency of a dependency)? This series was the bare minimum required to get the recipe to build. The build failed with "nothing provides nativesdk-foobar" without these.

Signature · 2 lines
Kind regards,
Luca Boccassi
#15 lore raw

PATCH 7/8 os-release: add nativesdk

In reply to [email protected]

From: Luca Boccassi <[email protected]>

Required to build systemd tools

---
 meta/recipes-core/os-release/os-release.bb | 2 ++
 1 file changed, 2 insertions(+)
meta/recipes-core/os-release/os-release.bb +2 -0
index 8847fe30c3..2f2aa66c46 100644
@@ -51,3 +51,5 @@ do_install () {
 }
 
 FILES:${PN} += "${nonarch_libdir}/os-release"
+
+BBCLASSEXTEND = "nativesdk"
Signature · 1 line
2.30.2
#16 lore raw

PATCH 8/8 systemd: add nativesdk

In reply to [email protected]

From: Luca Boccassi <[email protected]>

Allows using tools like systemd-analyze at build time and in CI systems

---
 meta/recipes-core/systemd/systemd-conf_1.0.bb    | 2 ++
 meta/recipes-core/systemd/systemd-serialgetty.bb | 2 ++
 meta/recipes-core/systemd/systemd_249.5.bb       | 2 ++
 3 files changed, 6 insertions(+)
meta/recipes-core/systemd/systemd-conf_1.0.bb +2 -0
index 61ce7939d3..84de4d17cf 100644
@@ -41,3 +41,5 @@ FILES:${PN} = "\
     ${systemd_unitdir}/system.conf.d/ \
     ${systemd_unitdir}/network/ \
 "
+
+BBCLASSEXTEND = "nativesdk"
meta/recipes-core/systemd/systemd-serialgetty.bb +2 -0
index 7ca951cdbd..f877e6ad18 100644
@@ -50,3 +50,5 @@ FILES:${PN} = "${systemd_system_unitdir}/*.service ${sysconfdir}"
 PACKAGE_ARCH = "${MACHINE_ARCH}"
 
 ALLOW_EMPTY:${PN} = "1"
+
+BBCLASSEXTEND = "nativesdk"
meta/recipes-core/systemd/systemd_249.5.bb +2 -0
index 016058cd7f..8f5c737152 100644
@@ -772,6 +772,8 @@ ALTERNATIVE_TARGET[runlevel] = "${base_bindir}/systemctl"
 ALTERNATIVE_LINK_NAME[runlevel] = "${base_sbindir}/runlevel"
 ALTERNATIVE_PRIORITY[runlevel] ?= "300"
 
+BBCLASSEXTEND = "nativesdk"
+
 # Nothing picks up /var in the nativesdk case
 do_install_append_class-nativesdk () {
 	rm -rf ${D}/var
Signature · 1 line
2.30.2
#17 lore raw
In reply to [email protected]

Shouldn't this be enabled in regular yocto builds first, e.g. allow systemd-native and then add the needed checks to systemd.bbclass? Maybe nativesdk support isn't then needed at all?

Alex

Quoted 44 lines · Luca Bocassi

From: Luca Boccassi <[email protected]>

systemd-analyze in the next release will gain the ability to run the 'security' and 'verify' verbs offline, on local units. This is very useful at build time and/or in CI systems to detect errors and issues before changes are deployed, as a static analyzer tool.
This series enables building the systemd recipe for the nativesdk targets, so that systemd-analyze can be included in the SDK and called by users/build systems/CI systems.

Luca Boccassi (8):
systemd: skip chown when building for nativesdk
systemd: skip postinst in nativesdk builds
systemd: remove /var in nativesdk builds
volatile-binds: remove /var in nativesdk builds
volatile-binds: add nativesdk
kbd: add nativesdk
os-release: add nativesdk
systemd: add nativesdk

 meta/recipes-core/kbd/kbd_2.4.0.bb            |  2 +-
 meta/recipes-core/os-release/os-release.bb    |  2 ++
 meta/recipes-core/systemd/systemd-conf_1.0.bb |  2 ++
 .../systemd/systemd-serialgetty.bb            |  2 ++
 meta/recipes-core/systemd/systemd_249.5.bb    | 29 +++++++++++++++++--
 .../volatile-binds/volatile-binds.bb          |  7 +++++
 6 files changed, 41 insertions(+), 3 deletions(-)

--
2.30.2

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group. View/Reply Online (#158384):
https://lists.openembedded.org/g/openembedded-core/message/158384
Mute This Topic: https://lists.openembedded.org/mt/87118013/1686489
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [ [email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

#18 lore raw
Quoted 5 lines · Alexander Kanavin

Shouldn't this be enabled in regular yocto builds first, e.g. allow systemd-native and then add the needed checks to systemd.bbclass? Maybe nativesdk support isn't then needed at all?

Alex

I'm not sure I follow, that would break the build? These changes are necessary to make it work. I am including the package in the local sdk configuration, without these patches it does not build.

Quoted 32 lines
Quoted 30 lines · Luca Bocassi

From: Luca Boccassi <[email protected]>

systemd-analyze in the next release will gain the ability to run the 'security' and 'verify' verbs offline, on local units. This is very useful at build time and/or in CI systems to detect errors and issues before changes are deployed, as a static analyzer tool.
This series enables building the systemd recipe for the nativesdk targets, so that systemd-analyze can be included in the SDK and called by users/build systems/CI systems.

Luca Boccassi (8):
  systemd: skip chown when building for nativesdk
  systemd: skip postinst in nativesdk builds
  systemd: remove /var in nativesdk builds
  volatile-binds: remove /var in nativesdk builds
  volatile-binds: add nativesdk
  kbd: add nativesdk
  os-release: add nativesdk
  systemd: add nativesdk

 meta/recipes-core/kbd/kbd_2.4.0.bb            |  2 +- meta/recipes-core/os-release/os-release.bb    |  2 ++ meta/recipes-core/systemd/systemd-conf_1.0.bb |  2 ++ .../systemd/systemd-serialgetty.bb            |  2 ++ meta/recipes-core/systemd/systemd_249.5.bb    | 29
+++++++++++++++++--
 .../volatile-binds/volatile-binds.bb          |  7 +++++

 6 files changed, 41 insertions(+), 3 deletions(-)
#19 lore raw
Quoted 11 lines · Luca Boccassi
Quoted 5 lines · Alexander Kanavin

Shouldn't this be enabled in regular yocto builds first, e.g. allow systemd-native and then add the needed checks to systemd.bbclass? Maybe nativesdk support isn't then needed at all?

Alex

I'm not sure I follow, that would break the build? These changes are necessary to make it work. I am including the package in the local sdk configuration, without these patches it does not build.

What I'm trying to say is running those systemd analyzers should be enabled in regular yocto builds first before it's enabled in SDKs. It's not a good idea to have a feature that is available in SDKs but not available in direct use of bitbake to build recipes.

Alex

Quoted 35 lines
Quoted 33 lines
Quoted 30 lines · Luca Bocassi

From: Luca Boccassi <[email protected]>

systemd-analyze in the next release will gain the ability to run the 'security' and 'verify' verbs offline, on local units. This is very useful at build time and/or in CI systems to detect errors and issues before changes are deployed, as a static analyzer tool.
This series enables building the systemd recipe for the nativesdk targets, so that systemd-analyze can be included in the SDK and called by users/build systems/CI systems.

Luca Boccassi (8):
systemd: skip chown when building for nativesdk
systemd: skip postinst in nativesdk builds
systemd: remove /var in nativesdk builds
volatile-binds: remove /var in nativesdk builds
volatile-binds: add nativesdk
kbd: add nativesdk
os-release: add nativesdk
systemd: add nativesdk

 meta/recipes-core/kbd/kbd_2.4.0.bb            |  2 +-
 meta/recipes-core/os-release/os-release.bb    |  2 ++
 meta/recipes-core/systemd/systemd-conf_1.0.bb |  2 ++
 .../systemd/systemd-serialgetty.bb            |  2 ++
 meta/recipes-core/systemd/systemd_249.5.bb    | 29
+++++++++++++++++--
 .../volatile-binds/volatile-binds.bb          |  7 +++++
 6 files changed, 41 insertions(+), 3 deletions(-)
#20 lore raw
Quoted 20 lines · Alexander Kanavin
Quoted 6 lines · Luca Boccassi
Quoted 1 line · Alexander Kanavin

Shouldn't this be enabled in regular yocto builds first, e.g.

allow

Quoted 3 lines

systemd-native and then add the needed checks to systemd.bbclass? Maybe nativesdk support isn't then needed at all?

Quoted 8 lines
Quoted 1 line

Alex

I'm not sure I follow, that would break the build? These changes are
necessary to make it work. I am including the package in the local sdk
configuration, without these patches it does not build.

Quoted 6 lines

What I'm trying to say is running those systemd analyzers should be enabled in regular yocto builds first before it's enabled in SDKs. It's not a good idea to have a feature that is available in SDKs but not available in direct use of bitbake to build recipes.

Alex

But it is already available? And it has been for a long time:

https://git.openembedded.org/openembedded-core/tree/meta/recipes-core/systemd/systemd_249.5.bb#n411

Quoted 37 lines
Quoted 37 lines
Quoted 2 lines

On Wed, 17 Nov 2021 at 13:32, Luca Bocassi

<[email protected]>

Quoted 6 lines
Quoted 5 lines · wrote:

From: Luca Boccassi <[email protected]>

systemd-analyze in the next release will gain the ability to run the 'security' and 'verify' verbs offline, on local units. This is very useful at build time and/or in CI systems to

detect

Quoted 3 lines
Quoted 3 lines

errors and issues before changes are deployed, as a static analyzer tool.
This series enables building the systemd recipe for the

nativesdk

Quoted 22 lines
Quoted 22 lines

targets, so that systemd-analyze can be included in the SDK and called by users/build systems/CI systems.

Luca Boccassi (8):
  systemd: skip chown when building for nativesdk
  systemd: skip postinst in nativesdk builds
  systemd: remove /var in nativesdk builds
  volatile-binds: remove /var in nativesdk builds
  volatile-binds: add nativesdk
  kbd: add nativesdk
  os-release: add nativesdk
  systemd: add nativesdk

 meta/recipes-core/kbd/kbd_2.4.0.bb            |  2 +- meta/recipes-core/os-release/os-release.bb    |  2 ++ meta/recipes-core/systemd/systemd-conf_1.0.bb |  2 ++ .../systemd/systemd-serialgetty.bb            |  2 ++ meta/recipes-core/systemd/systemd_249.5.bb    | 29
+++++++++++++++++--
 .../volatile-binds/volatile-binds.bb          |  7 +++++

 6 files changed, 41 insertions(+), 3 deletions(-)
#21 lore raw
Quoted 11 lines · Luca Boccassi
Quoted 6 lines

What I'm trying to say is running those systemd analyzers should be enabled in regular yocto builds first before it's enabled in SDKs. It's not a good idea to have a feature that is available in SDKs but not available in direct use of bitbake to build recipes.

Alex

But it is already available? And it has been for a long time:

https://git.openembedded.org/openembedded-core/tree/meta/recipes-core/systemd/systemd_249.5.bb#n411

This is packaging the tool for the target images; what I propose is that it's built and used natively.

Alex

#22 lore raw
Quoted 10 lines · Alexander Kanavin
Quoted 8 lines · Luca Boccassi
Quoted 1 line

What I'm trying to say is running those systemd analyzers should

be

Quoted 1 line

enabled in regular yocto builds first before it's enabled in

SDKs.

Quoted 1 line

It's not a good idea to have a feature that is available in SDKs

but

Quoted 2 lines

not available in direct use of bitbake to build recipes.

Quoted 8 lines
Quoted 5 lines
Quoted 1 line

Alex

But it is already available? And it has been for a long time:

https://git.openembedded.org/openembedded-core/tree/meta/recipes-core/systemd/systemd_249.5.bb#n411

This is packaging the tool for the target images; what I propose is that it's built and used natively.

Which is what this patchset does? Again you can't build these recipes to run locally without these changes, that's the entire point

Signature · 2 lines
Kind regards,
Luca Boccassi
#23 lore raw
Quoted 6 lines · Luca Boccassi
Quoted 2 lines

This is packaging the tool for the target images; what I propose is that it's built and used natively.

Which is what this patchset does? Again you can't build these recipes to run locally without these changes, that's the entire point

This patchset allows systemd binaries to be used in SDKs; what I would like to see is that those binaries are built and used directly in yocto builds. E.g. systemd recipe gains BBCLASSEXTEND = "native", systemd.bbclass gets DEPENDS = "systemd-native" and then uses the native systemd binaries in the same way you want to use them in your private SDK-based pipelines.

Alex

#24 lore raw
Quoted 10 lines · Alexander Kanavin
Quoted 7 lines · Luca Boccassi
Quoted 1 line

This is packaging the tool for the target images; what I propose

is

Quoted 1 line

that it's built and used natively.

Which is what this patchset does? Again you can't build these recipes
to run locally without these changes, that's the entire point

Quoted 6 lines

This patchset allows systemd binaries to be used in SDKs; what I would like to see is that those binaries are built and used directly in yocto builds. E.g. systemd recipe gains BBCLASSEXTEND = "native", systemd.bbclass gets DEPENDS = "systemd-native" and then uses the native systemd binaries in the same way you want to use them in your private SDK-based pipelines.

Sounds good to me, feel free to go ahead and send patches to do that. It's unrelated to this series and to my requirements, and I have no use for it, so I will not be spending any time chasing down various rabbit holes to make it work, sorry.

Signature · 2 lines
Kind regards,
Luca Boccassi
#25 lore raw
Quoted 7 lines · Luca Boccassi
Quoted 6 lines

This patchset allows systemd binaries to be used in SDKs; what I would like to see is that those binaries are built and used directly in yocto builds. E.g. systemd recipe gains BBCLASSEXTEND = "native", systemd.bbclass gets DEPENDS = "systemd-native" and then uses the native systemd binaries in the same way you want to use them in your private SDK-based pipelines.

Quoted 5 lines

Sounds good to me, feel free to go ahead and send patches to do that. It's unrelated to this series and to my requirements, and I have no use for it, so I will not be spending any time chasing down various rabbit holes to make it work, sorry.

Please consider the needs of the project and the community too. From that perspective I do think any QA enhancement must be available to users of bitbake before it's available to users of SDK (and even then, without any regression testing upstream, and only if they set up special SDK plumbing in private CI pipelines). Doing otherwise sets a bad precedent in my opinion.

Alex

#26 lore raw
In reply to [email protected]

Hi Luca,

If the real useful part is only about systemd-analyze in case of nativesdk/native, I'd suggest adding systemd-analyze-native or nativesdk-systemd-analyze instead of extending the current systemd recipe. This is because systemd has a whole bunch of dependencies which basically make no sense in case of native/nativesdk. Looking at the src/analyze/meson.build file, I guess it could be built independently.

Regards,
Qi

Quoted 38 lines · Luca Bocassi

From: Luca Boccassi <[email protected]>

systemd-analyze in the next release will gain the ability to run the 'security' and 'verify' verbs offline, on local units. This is very useful at build time and/or in CI systems to detect errors and issues before changes are deployed, as a static analyzer tool.
This series enables building the systemd recipe for the nativesdk targets, so that systemd-analyze can be included in the SDK and called by users/build systems/CI systems.

Luca Boccassi (8):
systemd: skip chown when building for nativesdk
systemd: skip postinst in nativesdk builds
systemd: remove /var in nativesdk builds
volatile-binds: remove /var in nativesdk builds
volatile-binds: add nativesdk
kbd: add nativesdk
os-release: add nativesdk
systemd: add nativesdk

  meta/recipes-core/kbd/kbd_2.4.0.bb            |  2 +-
  meta/recipes-core/os-release/os-release.bb    |  2 ++
  meta/recipes-core/systemd/systemd-conf_1.0.bb |  2 ++
  .../systemd/systemd-serialgetty.bb            |  2 ++
  meta/recipes-core/systemd/systemd_249.5.bb    | 29 +++++++++++++++++--
  .../volatile-binds/volatile-binds.bb          |  7 +++++
  6 files changed, 41 insertions(+), 3 deletions(-)

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#158384): https://lists.openembedded.org/g/openembedded-core/message/158384
Mute This Topic: https://lists.openembedded.org/mt/87118013/3618072
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

#27 lore raw
Quoted 11 lines · ChenQi

Hi Luca,

If the real useful part is only about systemd-analyze in case of nativesdk/native, I'd suggest adding systemd-analyze-native or nativesdk-systemd-analyze instead of extending the current systemd recipe.
This is because systemd has a whole bunch of dependencies which basically make no sense in case of native/nativesdk. Looking at the src/analyze/meson.build file, I guess it could be built independently.

Quoted 2 lines

Regards,
Qi

Hi,

Building individual binaries like that is not supported, so it cannot work.

Quoted 45 lines · Luca Bocassi

From: Luca Boccassi <[email protected]>

systemd-analyze in the next release will gain the ability to run the 'security' and 'verify' verbs offline, on local units. This is very useful at build time and/or in CI systems to detect errors and issues before changes are deployed, as a static analyzer tool.
This series enables building the systemd recipe for the nativesdk targets, so that systemd-analyze can be included in the SDK and called by users/build systems/CI systems.

Luca Boccassi (8):
  systemd: skip chown when building for nativesdk
  systemd: skip postinst in nativesdk builds
  systemd: remove /var in nativesdk builds
  volatile-binds: remove /var in nativesdk builds
  volatile-binds: add nativesdk
  kbd: add nativesdk
  os-release: add nativesdk
  systemd: add nativesdk

 meta/recipes-core/kbd/kbd_2.4.0.bb            |  2 +-
 meta/recipes-core/os-release/os-release.bb    |  2 ++
 meta/recipes-core/systemd/systemd-conf_1.0.bb |  2 ++
 .../systemd/systemd-serialgetty.bb            |  2 ++
 meta/recipes-core/systemd/systemd_249.5.bb    | 29
+++++++++++++++++--
 .../volatile-binds/volatile-binds.bb          |  7 +++++
 6 files changed, 41 insertions(+), 3 deletions(-)



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group. View/Reply Online (#158384):
https://lists.openembedded.org/g/openembedded-core/message/158384
Mute This Topic: https://lists.openembedded.org/mt/87118013/3618072
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

#28 lore raw
Quoted 12 lines · Luca Boccassi
Quoted 11 lines · ChenQi

Hi Luca,

If the real useful part is only about systemd-analyze in case of nativesdk/native, I'd suggest adding systemd-analyze-native or nativesdk-systemd-analyze instead of extending the current systemd recipe.
This is because systemd has a whole bunch of dependencies which basically make no sense in case of native/nativesdk. Looking at the src/analyze/meson.build file, I guess it could be built independently.

Quoted 6 lines
Quoted 2 lines

Regards,
Qi

Hi,

Building individual binaries like that is not supported, so it cannot work.

Thanks for your clarification.

Regards,

Qi

Quoted 45 lines
Quoted 45 lines · Luca Bocassi

From: Luca Boccassi <[email protected]>

systemd-analyze in the next release will gain the ability to run the 'security' and 'verify' verbs offline, on local units. This is very useful at build time and/or in CI systems to detect errors and issues before changes are deployed, as a static analyzer tool.
This series enables building the systemd recipe for the nativesdk targets, so that systemd-analyze can be included in the SDK and called by users/build systems/CI systems.

Luca Boccassi (8):
  systemd: skip chown when building for nativesdk
  systemd: skip postinst in nativesdk builds
  systemd: remove /var in nativesdk builds
  volatile-binds: remove /var in nativesdk builds
  volatile-binds: add nativesdk
  kbd: add nativesdk
  os-release: add nativesdk
  systemd: add nativesdk

  meta/recipes-core/kbd/kbd_2.4.0.bb            |  2 +-
  meta/recipes-core/os-release/os-release.bb    |  2 ++
  meta/recipes-core/systemd/systemd-conf_1.0.bb |  2 ++
  .../systemd/systemd-serialgetty.bb            |  2 ++
  meta/recipes-core/systemd/systemd_249.5.bb    | 29
+++++++++++++++++--
  .../volatile-binds/volatile-binds.bb          |  7 +++++
  6 files changed, 41 insertions(+), 3 deletions(-)

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group. View/Reply Online (#158384):
https://lists.openembedded.org/g/openembedded-core/message/158384
Mute This Topic: https://lists.openembedded.org/mt/87118013/3618072
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

#29 lore raw

PATCH v2 1/7 systemd: skip chown when building for nativesdk

In reply to [email protected]

From: Luca Boccassi <[email protected]>

The useradd class is a no-op in the nativesdk case, so chown will fail. Skip them.

---
v2: use "${PN}" = "${BPN}" as suggested by reviewers

 meta/recipes-core/systemd/systemd_249.5.bb | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)
meta/recipes-core/systemd/systemd_249.5.bb +8 -2
index 8bdc0ca028..2df2de0cf3 100644
@@ -275,7 +275,10 @@ do_install() {
 		# which is expected to be empty.
 		rm -rf ${D}${localstatedir}/log
 	else
-		chown root:systemd-journal ${D}${localstatedir}/log/journal
+		# The useradd class is a no-op in the nativesdk case, so chown will fail
+		if [ "${PN}" = "${BPN}" ]; then
+			chown root:systemd-journal ${D}${localstatedir}/log/journal
+		fi
 
 		# journal-remote creates this at start
 		rm -rf ${D}${localstatedir}/log/journal/remote
@@ -319,7 +322,10 @@ do_install() {
 	if ${@bb.utils.contains('PACKAGECONFIG', 'polkit', 'true', 'false', d)}; then
 		if [ -d ${D}${datadir}/polkit-1/rules.d ]; then
 			chmod 700 ${D}${datadir}/polkit-1/rules.d
-			chown polkitd:root ${D}${datadir}/polkit-1/rules.d
+			# The useradd class is a no-op in the nativesdk case, so chown will fail
+			if [ "${PN}" = "${BPN}" ]; then
+				chown polkitd:root ${D}${datadir}/polkit-1/rules.d
+			fi
 		fi
 	fi
 
Signature · 1 line
2.30.2
#30 lore raw

PATCH v2 2/7 systemd: skip postinst in nativesdk builds

From: Luca Boccassi <[email protected]>

They will fail, as there's nowhere to run them

---
v2: use "${PN}" = "${BPN}" as suggested by reviewers

 meta/recipes-core/systemd/systemd_249.5.bb | 12 ++++++++++++
 1 file changed, 12 insertions(+)
meta/recipes-core/systemd/systemd_249.5.bb +12 -0
index 2df2de0cf3..ec9c350297 100644
@@ -773,12 +773,18 @@ ALTERNATIVE_LINK_NAME[runlevel] = "${base_sbindir}/runlevel"
 ALTERNATIVE_PRIORITY[runlevel] ?= "300"
 
 pkg_postinst:${PN}:libc-glibc () {
+	if [ "${PN}" != "${BPN}" ]; then
+		exit 0
+	fi
 	sed -e '/^hosts:/s/\s*\<myhostname\>//' \
 		-e 's/\(^hosts:.*\)\(\<files\>\)\(.*\)\(\<dns\>\)\(.*\)/\1\2 myhostname \3\4\5/' \
 		-i $D${sysconfdir}/nsswitch.conf
 }
 
 pkg_prerm:${PN}:libc-glibc () {
+	if [ "${PN}" != "${BPN}" ]; then
+		exit 0
+	fi
 	sed -e '/^hosts:/s/\s*\<myhostname\>//' \
 		-e '/^hosts:/s/\s*myhostname//' \
 		-i $D${sysconfdir}/nsswitch.conf
@@ -786,6 +792,9 @@ pkg_prerm:${PN}:libc-glibc () {
 
 PACKAGE_WRITE_DEPS += "qemu-native"
 pkg_postinst:udev-hwdb () {
+	if [ "${PN}" != "${BPN}" ]; then
+		exit 0
+	fi
 	if test -n "$D"; then
 		$INTERCEPT_DIR/postinst_intercept update_udev_hwdb ${PKG} mlprefix=${MLPREFIX} binprefix=${MLPREFIX} rootlibexecdir="${rootlibexecdir}" PREFERRED_PROVIDER_udev="${PREFERRED_PROVIDER_udev}"
 	else
@@ -794,5 +803,8 @@ pkg_postinst:udev-hwdb () {
 }
 
 pkg_prerm:udev-hwdb () {
+	if [ "${PN}" != "${BPN}" ]; then
+		exit 0
+	fi
 	rm -f $D${sysconfdir}/udev/hwdb.bin
 }
Signature · 1 line
2.30.2
#31 lore raw

PATCH v2 3/7 systemd: remove /var in nativesdk builds

In reply to [email protected]

From: Luca Boccassi <[email protected]>

Nothing picks it up, so it fails QA checks

---
 meta/recipes-core/systemd/systemd_249.5.bb | 5 +++++
 1 file changed, 5 insertions(+)
meta/recipes-core/systemd/systemd_249.5.bb +5 -0
index ec9c350297..9993036aac 100644
@@ -772,6 +772,11 @@ ALTERNATIVE_TARGET[runlevel] = "${base_bindir}/systemctl"
 ALTERNATIVE_LINK_NAME[runlevel] = "${base_sbindir}/runlevel"
 ALTERNATIVE_PRIORITY[runlevel] ?= "300"
 
+# Nothing picks up /var in the nativesdk case
+do_install_append_class-nativesdk () {
+	rm -rf ${D}/var
+}
+
 pkg_postinst:${PN}:libc-glibc () {
 	if [ "${PN}" != "${BPN}" ]; then
 		exit 0
Signature · 1 line
2.30.2
#32 lore raw

PATCH v2 4/7 systemd: remove volatile-binds RDEPENDS for nativesdk

In reply to [email protected]

From: Luca Boccassi <[email protected]>

Not needed for SDK binaries

---
v2: remove dependency instead of adding nativesdk to volatile-binds

 meta/recipes-core/systemd/systemd_249.5.bb | 1 +
 1 file changed, 1 insertion(+)
meta/recipes-core/systemd/systemd_249.5.bb +1 -0
index 9993036aac..2928a85c93 100644
@@ -644,6 +644,7 @@ FILES:${PN}-dev += "${base_libdir}/security/*.la ${datadir}/dbus-1/interfaces/ $
 RDEPENDS:${PN} += "kmod dbus util-linux-mount util-linux-umount udev (= ${EXTENDPKGV}) systemd-udev-rules util-linux-agetty util-linux-fsck"
 RDEPENDS:${PN} += "${@bb.utils.contains('PACKAGECONFIG', 'serial-getty-generator', '', 'systemd-serialgetty', d)}"
 RDEPENDS:${PN} += "volatile-binds"
+RDEPENDS_${PN}_remove_class-nativesdk = "volatile-binds"
 
 RRECOMMENDS:${PN} += "systemd-extra-utils \
                       udev-hwdb \
Signature · 1 line
2.30.2
#33 lore raw

Re: [OE-core] [PATCH v2 4/7] systemd: remove volatile-binds RDEPENDS for nativesdk

Quoted 16 lines · Luca Bocassi

From: Luca Boccassi <[email protected]>

Not needed for SDK binaries

---
v2: remove dependency instead of adding nativesdk to volatile-binds

 meta/recipes-core/systemd/systemd_249.5.bb | 1 +
 1 file changed, 1 insertion(+)
meta/recipes-core/systemd/systemd_249.5.bb +0 -0
index 9993036aac..2928a85c93 100644

meta/recipes-core/systemd/systemd_249.5.bb FILES:${PN}-dev += "${base_libdir}/security/*.la ${datadir}/dbus-1/interfaces/ $ · line 650

Quoted 7 lines
meta/recipes-core/systemd/systemd_249.5.bb +1 -0
@@ -644,6 +644,7 @@ FILES:${PN}-dev += "${base_libdir}/security/*.la ${datadir}/dbus-1/interfaces/ $
 RDEPENDS:${PN} += "kmod dbus util-linux-mount util-linux-umount udev (= ${EXTENDPKGV}) systemd-udev-rules util-linux-agetty util-linux-fsck"
 RDEPENDS:${PN} += "${@bb.utils.contains('PACKAGECONFIG', 'serial-getty-generator', '', 'systemd-serialgetty', d)}"
 RDEPENDS:${PN} += "volatile-binds"
+RDEPENDS_${PN}_remove_class-nativesdk = "volatile-binds"
 
 RRECOMMENDS:${PN} += "systemd-extra-utils \
                       udev-hwdb \

This patch raises a few questions like how this is being tested?

The override syntax changed so the avoid would never have worked with master.

Also, I have a strong preference for not using remove operators in OE-Core, you can usually rearrange things so that it isn't necessary. The reason for that is that it is very hard to override these operations. I know we do have some but minimising them is good.

Cheers,

Richard

#34 lore raw

Re: [OE-core] [PATCH v2 4/7] systemd: remove volatile-binds RDEPENDS for nativesdk

Quoted 43 lines · Richard Purdie
Quoted 20 lines · Luca Bocassi

From: Luca Boccassi <[email protected]>

Not needed for SDK binaries

---
v2: remove dependency instead of adding nativesdk to volatile-binds

 meta/recipes-core/systemd/systemd_249.5.bb | 1 +

 1 file changed, 1 insertion(+)
meta/recipes-core/systemd/systemd_249.5.bb +0 -0
index 9993036aac..2928a85c93 100644
@@ -644,6 +644,7 @@ FILES:${PN}-dev +=

"${base_libdir}/security/*.la ${datadir}/dbus-1/interfaces/ $ RDEPENDS:${PN} += "kmod dbus util-linux-mount util-linux-umount udev (= ${EXTENDPKGV}) systemd-udev-rules util-linux-agetty util-

Quoted 8 lines

linux-fsck"
 RDEPENDS:${PN} += "${@bb.utils.contains('PACKAGECONFIG', 'serial- getty-generator', '', 'systemd-serialgetty', d)}" RDEPENDS:${PN} += "volatile-binds" +RDEPENDS_${PN}_remove_class-nativesdk = "volatile-binds"
 RRECOMMENDS:${PN} += "systemd-extra-utils \
                       udev-hwdb \

This patch raises a few questions like how this is being tested?

The override syntax changed so the avoid would never have worked with master.

Also, I have a strong preference for not using remove operators in OE-Core, you
can usually rearrange things so that it isn't necessary. The reason for that is
that it is very hard to override these operations. I know we do have some but
minimising them is good.

Quoted 3 lines

Cheers,

Richard

It was tested in a downstream dunfell branch, since that's what our build system supports. I was not aware there had been a backward incompatible syntax change, thanks for the hint.

Signature · 2 lines
Kind regards,
Luca Boccassi
#35 lore raw

PATCH v2 5/7 kbd: add nativesdk

In reply to [email protected]

From: Luca Boccassi <[email protected]>

Required to build systemd tools

---
 meta/recipes-core/kbd/kbd_2.4.0.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
meta/recipes-core/kbd/kbd_2.4.0.bb +1 -1
index 7cb45eff77..7efc7af312 100644
@@ -43,4 +43,4 @@ ALTERNATIVE:${PN} = "chvt deallocvt fgconsole openvt showkey \
                      ${@bb.utils.contains('DISTRO_FEATURES', 'pam', 'vlock','', d)}"
 ALTERNATIVE_PRIORITY = "100"
 
-BBCLASSEXTEND = "native"
+BBCLASSEXTEND = "native nativesdk"
Signature · 1 line
2.30.2
#36 lore raw

PATCH v2 6/7 os-release: add nativesdk

In reply to [email protected]

From: Luca Boccassi <[email protected]>

Required to build systemd tools

---
 meta/recipes-core/os-release/os-release.bb | 2 ++
 1 file changed, 2 insertions(+)
meta/recipes-core/os-release/os-release.bb +2 -0
index 8847fe30c3..2f2aa66c46 100644
@@ -51,3 +51,5 @@ do_install () {
 }
 
 FILES:${PN} += "${nonarch_libdir}/os-release"
+
+BBCLASSEXTEND = "nativesdk"
Signature · 1 line
2.30.2
#37 lore raw

PATCH v2 7/7 systemd: add nativesdk

In reply to [email protected]

From: Luca Boccassi <[email protected]>

Allows using tools like systemd-analyze at build time and in CI systems

---
 meta/recipes-core/systemd/systemd-conf_1.0.bb    | 2 ++
 meta/recipes-core/systemd/systemd-serialgetty.bb | 2 ++
 meta/recipes-core/systemd/systemd_249.5.bb       | 2 ++
 3 files changed, 6 insertions(+)
meta/recipes-core/systemd/systemd-conf_1.0.bb +2 -0
index 61ce7939d3..84de4d17cf 100644
@@ -41,3 +41,5 @@ FILES:${PN} = "\
     ${systemd_unitdir}/system.conf.d/ \
     ${systemd_unitdir}/network/ \
 "
+
+BBCLASSEXTEND = "nativesdk"
meta/recipes-core/systemd/systemd-serialgetty.bb +2 -0
index 7ca951cdbd..f877e6ad18 100644
@@ -50,3 +50,5 @@ FILES:${PN} = "${systemd_system_unitdir}/*.service ${sysconfdir}"
 PACKAGE_ARCH = "${MACHINE_ARCH}"
 
 ALLOW_EMPTY:${PN} = "1"
+
+BBCLASSEXTEND = "nativesdk"
meta/recipes-core/systemd/systemd_249.5.bb +2 -0
index 2928a85c93..445a50b1e3 100644
@@ -773,6 +773,8 @@ ALTERNATIVE_TARGET[runlevel] = "${base_bindir}/systemctl"
 ALTERNATIVE_LINK_NAME[runlevel] = "${base_sbindir}/runlevel"
 ALTERNATIVE_PRIORITY[runlevel] ?= "300"
 
+BBCLASSEXTEND = "nativesdk"
+
 # Nothing picks up /var in the nativesdk case
 do_install_append_class-nativesdk () {
 	rm -rf ${D}/var
Signature · 1 line
2.30.2
#38 lore raw

Re: [OE-core] [PATCH v2 7/7] systemd: add nativesdk

Once again, I do not want this accepted in oe-core, not until there's equivalent native functionality.

Alex

Quoted 65 lines · Luca Bocassi

From: Luca Boccassi <[email protected]>

Allows using tools like systemd-analyze at build time and in CI systems

---
 meta/recipes-core/systemd/systemd-conf_1.0.bb    | 2 ++
 meta/recipes-core/systemd/systemd-serialgetty.bb | 2 ++
 meta/recipes-core/systemd/systemd_249.5.bb       | 2 ++
 3 files changed, 6 insertions(+)
meta/recipes-core/systemd/systemd-conf_1.0.bb +2 -0
index 61ce7939d3..84de4d17cf 100644
@@ -41,3 +41,5 @@ FILES:${PN} = "\
     ${systemd_unitdir}/system.conf.d/ \
     ${systemd_unitdir}/network/ \
 "
+
+BBCLASSEXTEND = "nativesdk"
meta/recipes-core/systemd/systemd-serialgetty.bb +0 -0
index 7ca951cdbd..f877e6ad18 100644
@@ -50,3 +50,5 @@ FILES:${PN} = "${systemd_system_unitdir}/*.service

${sysconfdir}"
PACKAGE_ARCH = "${MACHINE_ARCH}"

ALLOW_EMPTY:${PN} = "1"

meta/recipes-core/systemd/systemd-serialgetty.bb +2 -0
+
+BBCLASSEXTEND = "nativesdk"
meta/recipes-core/systemd/systemd_249.5.bb +0 -0
index 2928a85c93..445a50b1e3 100644
@@ -773,6 +773,8 @@ ALTERNATIVE_TARGET[runlevel] =

"${base_bindir}/systemctl"
ALTERNATIVE_LINK_NAME[runlevel] = "${base_sbindir}/runlevel" ALTERNATIVE_PRIORITY[runlevel] ?= "300"

meta/recipes-core/systemd/systemd_249.5.bb +2 -1
+BBCLASSEXTEND = "nativesdk"
+
 # Nothing picks up /var in the nativesdk case
 do_install_append_class-nativesdk () {
        rm -rf ${D}/var
--

2.30.2

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group. View/Reply Online (#158513):
https://lists.openembedded.org/g/openembedded-core/message/158513
Mute This Topic: https://lists.openembedded.org/mt/87165499/1686489
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [ [email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

#39 lore raw

Re: [OE-core] [PATCH v2 7/7] systemd: add nativesdk

Quoted 4 lines · Alexander Kanavin

Once again, I do not want this accepted in oe-core, not until there's equivalent native functionality.

Alex

As already mentioned, that's completely unrelated, and I do not have the time nor the interest to invest weeks of my time working on that. But arbitrarily rejecting patches is your prerogative of course, so I'll just keep these changes out-of-tree then.

Quoted 52 lines
Quoted 50 lines · Luca Bocassi

From: Luca Boccassi <[email protected]>

Allows using tools like systemd-analyze at build time and in CI systems

---
 meta/recipes-core/systemd/systemd-conf_1.0.bb    | 2 ++ meta/recipes-core/systemd/systemd-serialgetty.bb | 2 ++ meta/recipes-core/systemd/systemd_249.5.bb       | 2 ++

 3 files changed, 6 insertions(+)
meta/recipes-core/systemd/systemd-conf_1.0.bb +0 -0
index 61ce7939d3..84de4d17cf 100644
@@ -41,3 +41,5 @@ FILES:${PN} = "\
      ${systemd_unitdir}/system.conf.d/ \
      ${systemd_unitdir}/network/ \

 "

meta/recipes-core/systemd/systemd-conf_1.0.bb +2 -0
+
+BBCLASSEXTEND = "nativesdk"
meta/recipes-core/systemd/systemd-serialgetty.bb +0 -0
index 7ca951cdbd..f877e6ad18 100644
@@ -50,3 +50,5 @@ FILES:${PN} =

"${systemd_system_unitdir}/*.service ${sysconfdir}" PACKAGE_ARCH = "${MACHINE_ARCH}"

 ALLOW_EMPTY:${PN} = "1"

meta/recipes-core/systemd/systemd-serialgetty.bb +2 -0
+
+BBCLASSEXTEND = "nativesdk"
meta/recipes-core/systemd/systemd_249.5.bb +0 -0
index 2928a85c93..445a50b1e3 100644
@@ -773,6 +773,8 @@ ALTERNATIVE_TARGET[runlevel] =

"${base_bindir}/systemctl" ALTERNATIVE_LINK_NAME[runlevel] = "${base_sbindir}/runlevel" ALTERNATIVE_PRIORITY[runlevel] ?= "300"

meta/recipes-core/systemd/systemd_249.5.bb +2 -0
+BBCLASSEXTEND = "nativesdk"
+

 # Nothing picks up /var in the nativesdk case
 do_install_append_class-nativesdk () {
        rm -rf ${D}/var

#40 lore raw

Re: [OE-core] [PATCH v2 1/7] systemd: skip chown when building for nativesdk

In reply to [email protected]
Quoted 8 lines · Luca Bocassi

From: Luca Boccassi <[email protected]>

The useradd class is a no-op in the nativesdk case, so chown will fail. Skip them.

---
v2: use "${PN}" = "${BPN}" as suggested by reviewers

I think that was bad advice since this would break multilib variants of the systemd recipe and I'd much prefer this was conditional on nativesdk.

Quoted 9 lines
 meta/recipes-core/systemd/systemd_249.5.bb | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)
meta/recipes-core/systemd/systemd_249.5.bb +0 -0
index 8bdc0ca028..2df2de0cf3 100644
@@ -275,7 +275,10 @@ do_install() {
 		# which is expected to be empty.

meta/recipes-core/systemd/systemd_249.5.bb do_install() { · line 284

Quoted 10 lines
meta/recipes-core/systemd/systemd_249.5.bb +4 -1
 		rm -rf ${D}${localstatedir}/log
 	else
-		chown root:systemd-journal ${D}${localstatedir}/log/journal
+		# The useradd class is a no-op in the nativesdk case, so chown will fail
+		if [ "${PN}" = "${BPN}" ]; then
+			chown root:systemd-journal ${D}${localstatedir}/log/journal
+		fi
 
 		# journal-remote creates this at start
 		rm -rf ${D}${localstatedir}/log/journal/remote

I'm guessing this is only failing on systems that don't have a systemd-jounral group as it built ok for me?

The better way to fix this is probably to replicate what we have for native, i.e. the entry in the class:

native.bbclass:PATH:prepend = "${COREBASE}/scripts/native-intercept:"

which puts a chown and chgrp into PATH which doesn't do anything. We could do something similar for nativesdk and it would avoid the need for these if statements and solve the problem generically.

I am also a bit concerned about some of the other "creeping" dependencies so I experimented a little with master to see how much it could be cut down. I could get working builds with the lines below:

"""
PACKAGECONFIG:remove:class-native = "vconsole xkbcommon sysvinit" PACKAGECONFIG:append:class-native = " serial-getty-generator" RDEPENDS:${PN}:remove:class-native = "volatile-binds" RRECOMMENDS:${PN}:remove:class-native = "os-release systemd-conf" RRECOMMENDS:${PN}-vconsole-setup:class-native = ""

PACKAGECONFIG:remove:class-nativesdk = "vconsole xkbcommon sysvinit" PACKAGECONFIG:append:class-nativesdk = " serial-getty-generator" RDEPENDS:${PN}:remove:class-nativesdk = "volatile-binds" RRECOMMENDS:${PN}:remove:class-nativesdk = "os-release systemd-conf" RRECOMMENDS:${PN}-vconsole-setup:class-nativesdk = ""

# Nothing picks up /var in the nativesdk case

do_install:append:class-nativesdk () {
       rm -rf ${D}/var
}

BBCLASSEXTEND = "native nativesdk"
"""

which removes the need to change os-release, kbd, systemd-conf and systemd- getty. To merge, we'd want to restructure this to alter the variable construction so we can avoid the use of the remove operator but it is an easy way to test and evaluate the extent of changes needed.

The above also nearly has native builds working as well. To get that to build I had to patch meson.build:

Index: git/meson.build
===================================================================
--- git.orig/meson.buildIndex: git/meson.build
===================================================================

meson.build +1 -1
@@ -745,7 +745,7 @@ conf.set('CONTAINER_UID_BASE_MAX', conta
 nobody_user = get_option('nobody-user')
 nobody_group = get_option('nobody-group')
 
-if not meson.is_cross_build()
+if false and not meson.is_cross_build()
         getent_result = run_command('getent', 'passwd', '65534')
         if getent_result.returncode() == 0
                 name = getent_result.stdout().split(':')[0]

since we want to use the "cross" codepath there regardless. That lets everything build but I did then see errors due to absolute path symlinks which would likely be fixable.

I did this mainly as I wanted to understand how much of systemd is being build and packaged since many of these packages will not make sense in a SDK or a native build. I think the final piece of patch which we'd need to be able to merge something like this is to trim down what is being packaged up to the pieces which are actually useful in the native or nativesdk cases.

Cheers,

Richard

#41 lore raw

Re: [OE-core] [PATCH v2 1/7] systemd: skip chown when building for nativesdk

In reply to [email protected]

I have sort of a general question regarding this patch series.

Last time I checked (and yeah it's been a while back) systemd-analyze wasn't self-containing, meaning it would have to have a running systemd process and at least a running dbus iirc.

Is that still the case?
If yes, how should that work here?
Do we want to spawn a systemd per workspace/SDK?
What about the weird setting that systemd somehow requires us to assign PID 1 to it? What about systems that have already a systemd instance running - and what about the systems that don't?

And if not (and all of sudden systemd project finally decided to recognize the cross-compile use case), does this only apply to systemd-analyze?

I would be happy if you could shed some light on these questions. Thx

Quoted 51 lines · Luca Bocassi

From: Luca Boccassi <[email protected]>

The useradd class is a no-op in the nativesdk case, so chown will fail. Skip them.

---
v2: use "${PN}" = "${BPN}" as suggested by reviewers

  meta/recipes-core/systemd/systemd_249.5.bb | 10 ++++++++--
  1 file changed, 8 insertions(+), 2 deletions(-)
meta/recipes-core/systemd/systemd_249.5.bb +8 -3
index 8bdc0ca028..2df2de0cf3 100644
@@ -275,7 +275,10 @@ do_install() {
  		# which is expected to be empty.
  		rm -rf ${D}${localstatedir}/log
  	else
-		chown root:systemd-journal ${D}${localstatedir}/log/journal
+		# The useradd class is a no-op in the nativesdk case, so chown will fail
+		if [ "${PN}" = "${BPN}" ]; then
+			chown root:systemd-journal ${D}${localstatedir}/log/journal
+		fi
 
  		# journal-remote creates this at start
  		rm -rf ${D}${localstatedir}/log/journal/remote
@@ -319,7 +322,10 @@ do_install() {
  	if ${@bb.utils.contains('PACKAGECONFIG', 'polkit', 'true', 'false', d)}; then
  		if [ -d ${D}${datadir}/polkit-1/rules.d ]; then
  			chmod 700 ${D}${datadir}/polkit-1/rules.d
-			chown polkitd:root ${D}${datadir}/polkit-1/rules.d
+			# The useradd class is a no-op in the nativesdk case, so chown will fail
+			if [ "${PN}" = "${BPN}" ]; then
+				chown polkitd:root ${D}${datadir}/polkit-1/rules.d
+			fi
  		fi
  	fi
 
 
 
 
-=-=-=-=-=-=-=-=-=-=-=-

Links: You receive all messages sent to this group.
View/Reply Online (#158507): https://lists.openembedded.org/g/openembedded-core/message/158507
Mute This Topic: https://lists.openembedded.org/mt/87165491/3647476
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

#42 lore raw

Re: [OE-core] [PATCH v2 1/7] systemd: skip chown when building for nativesdk

Indeed; in the absence of tests that exercise this functionality - either SDK tests, or direct bitbake tests - it's hard to say if
this is an experiment that may not be sustainable long term, or something systemd upstream is actually committed to.

Alex

Quoted 84 lines · Konrad Weihmann

I have sort of a general question regarding this patch series.

Last time I checked (and yeah it's been a while back) systemd-analyze wasn't self-containing, meaning it would have to have a running systemd process and at least a running dbus iirc.

Is that still the case?
If yes, how should that work here?
Do we want to spawn a systemd per workspace/SDK?
What about the weird setting that systemd somehow requires us to assign PID 1 to it?
What about systems that have already a systemd instance running - and what about the systems that don't?

And if not (and all of sudden systemd project finally decided to recognize the cross-compile use case), does this only apply to systemd-analyze?

I would be happy if you could shed some light on these questions. Thx

Quoted 5 lines · Luca Bocassi

From: Luca Boccassi <[email protected]>

The useradd class is a no-op in the nativesdk case, so chown will fail. Skip them.

Review

Quoted 8 lines

---
v2: use "${PN}" = "${BPN}" as suggested by reviewers

  meta/recipes-core/systemd/systemd_249.5.bb | 10 ++++++++--
  1 file changed, 8 insertions(+), 2 deletions(-)
(quoted diff) +0 -0

b/meta/recipes-core/systemd/systemd_249.5.bb

meta/recipes-core/systemd/systemd_249.5.bb do_install() { · line 278

Quoted 9 lines

index 8bdc0ca028..2df2de0cf3 100644

meta/recipes-core/systemd/systemd_249.5.bb +1 -1
@@ -275,7 +275,10 @@ do_install() {
              # which is expected to be empty.
              rm -rf ${D}${localstatedir}/log
      else
-             chown root:systemd-journal ${D}${localstatedir}/log/journal
+             # The useradd class is a no-op in the nativesdk case, so

chown will fail

meta/recipes-core/systemd/systemd_249.5.bb do_install() { · line 280

Quoted 2 lines
meta/recipes-core/systemd/systemd_249.5.bb +2 -0
+             if [ "${PN}" = "${BPN}" ]; then
+                     chown root:systemd-journal

${D}${localstatedir}/log/journal

meta/recipes-core/systemd/systemd_249.5.bb do_install() { · line 322

Quoted 6 lines
meta/recipes-core/systemd/systemd_249.5.bb +1 -0
+             fi
 
              # journal-remote creates this at start
              rm -rf ${D}${localstatedir}/log/journal/remote
@@ -319,7 +322,10 @@ do_install() {
      if ${@bb.utils.contains('PACKAGECONFIG', 'polkit', 'true',

'false', d)}; then

meta/recipes-core/systemd/systemd_249.5.bb do_install() {

Quoted 4 lines
meta/recipes-core/systemd/systemd_249.5.bb +1 -1
              if [ -d ${D}${datadir}/polkit-1/rules.d ]; then
                      chmod 700 ${D}${datadir}/polkit-1/rules.d
-                     chown polkitd:root ${D}${datadir}/polkit-1/rules.d
+                     # The useradd class is a no-op in the nativesdk

case, so chown will fail

meta/recipes-core/systemd/systemd_249.5.bb do_install() { · line 327

Quoted 2 lines
meta/recipes-core/systemd/systemd_249.5.bb +2 -0
+                     if [ "${PN}" = "${BPN}" ]; then
+                             chown polkitd:root

${D}${datadir}/polkit-1/rules.d

meta/recipes-core/systemd/systemd_249.5.bb do_install() { · line 331

Quoted 9 lines
meta/recipes-core/systemd/systemd_249.5.bb +1 -0
+                     fi
              fi
      fi
 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group. View/Reply Online (#158569):
https://lists.openembedded.org/g/openembedded-core/message/158569
Mute This Topic: https://lists.openembedded.org/mt/87165491/1686489
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [ [email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

#43 lore raw

Re: [OE-core] [PATCH v2 1/7] systemd: skip chown when building for nativesdk

In reply to Konrad Weihmann
Quoted 8 lines · Konrad Weihmann

I have sort of a general question regarding this patch series.

Last time I checked (and yeah it's been a while back) systemd-analyze wasn't self-containing, meaning it would have to have a running systemd
process and at least a running dbus iirc.

Is that still the case?

That was the case only for some verbs - 'verify' does not need a running instance. From v250 (next release) it will also be able to operate on images/root directories.
The 'security' verb did need a running instance, but there's a new -- offline switch in v250.

Signature · 2 lines
Kind regards,
Luca Boccassi
#44 lore raw

Re: [OE-core] [PATCH v2 1/7] systemd: skip chown when building for nativesdk

Quoted 8 lines · Luca Boccassi
Quoted 7 lines · Konrad Weihmann

I have sort of a general question regarding this patch series.

Last time I checked (and yeah it's been a while back) systemd-analyze wasn't self-containing, meaning it would have to have a running systemd
process and at least a running dbus iirc.

Quoted 8 lines
Quoted 1 line

Is that still the case?

That was the case only for some verbs - 'verify' does not need a running instance. From v250 (next release) it will also be able to operate on images/root directories.
The 'security' verb did need a running instance, but there's a new -- offline switch in v250.

Thanks for the background information.
I kind of agree with the voices raised in the discussion so far.

As the feature will be available only in a yet to be released version, I would propose to

- wait for the release of systemd 2.50
- build a native variant of the tools first
- package only what is really suitable for "offline" use
- add a nativesdk variant later on

And I think there should be some demo patch to use maybe the analyze part in insane bbclass or so, so we could first of all see the actual benefit of it and even more important can easily track down future regressions.

BTW you said you tested this primary on dunfell, what kind of makes me think how these pieces fit together, as dunfell (likely) will never get the support for the tools mentioned

#45 lore raw

Re: [OE-core] [PATCH v2 1/7] systemd: skip chown when building for nativesdk

Quoted 30 lines · Konrad Weihmann
Quoted 8 lines · Luca Boccassi
Quoted 7 lines · Konrad Weihmann

I have sort of a general question regarding this patch series.

Last time I checked (and yeah it's been a while back) systemd-analyze wasn't self-containing, meaning it would have to have a running systemd
process and at least a running dbus iirc.

Quoted 8 lines
Quoted 1 line

Is that still the case?

That was the case only for some verbs - 'verify' does not need a running instance. From v250 (next release) it will also be able to operate on images/root directories.
The 'security' verb did need a running instance, but there's a new -- offline switch in v250.

Thanks for the background information.
I kind of agree with the voices raised in the discussion so far.

As the feature will be available only in a yet to be released version, I would propose to

- wait for the release of systemd 2.50
- build a native variant of the tools first
- package only what is really suitable for "offline" use
- add a nativesdk variant later on

Quoted 4 lines

And I think there should be some demo patch to use maybe the analyze part in insane bbclass or so, so we could first of all see the actual benefit of it and even more important can easily track down future regressions.

As mentioned earlier, I have no use for 'native' variants and whatever an 'insane bbclass' is, so I will not be spending several weeks to make these things work, sorry. I've got no issue at all if you don't want to take this series, it's absolutely fine, all of these changes can be done via bbappend anyway. My experience of working with yocto software is so horribly painful and time-consuming that I'm not going to spend one minute more on it than I have to.

Quoted 3 lines

BTW you said you tested this primary on dunfell, what kind of makes me think how these pieces fit together, as dunfell (likely) will never get the support for the tools mentioned

It's tested _only_ on dunfell. We forwarded the systemd recipe to v247 on top of it, and then additional patches including the ones for this functionality are backported. It's very easy to backport them, if you are curious you can see the whole tree here:
https://github.com/bluca/systemd/commits/dunfell-msft-247

Signature · 2 lines
Kind regards,
Luca Boccassi