I have two small questions.

1) For the current systemd, what's the difference between the final configure results with/without this option?
2) How could this help avoid reproducibility issues?

Regards,
Qi

On 11/10/24 21:28, Markus Volk wrote:
This might help avoid reproducibility issues

Signed-off-by: Markus Volk <[email protected]>
---
  meta/recipes-core/systemd/systemd_256.7.bb | 1 +
  1 file changed, 1 insertion(+)

diff --git a/meta/recipes-core/systemd/systemd_256.7.bb 
b/meta/recipes-core/systemd/systemd_256.7.bb
index bf829c4931..159a0e25b8 100644
--- a/meta/recipes-core/systemd/systemd_256.7.bb
+++ b/meta/recipes-core/systemd/systemd_256.7.bb
@@ -258,6 +258,7 @@ EXTRA_OEMESON += "-Dnobody-user=nobody \
                    -Dsystem-gid-max=999 \
                    -Dcreate-log-dirs=false \
                    ${@bb.utils.contains('DISTRO_FEATURES', 'zeroconf', 
'-Ddefault-mdns=no -Ddefault-llmnr=no', '', d)} \
+                  --auto-features=disabled \
                    "
# Hardcode target binary paths to avoid using paths from sysroot or worse




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

Reply via email to