public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Zoltán Böszörményi" <zboszor@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: "Zoltán Böszörményi" <zboszor@gmail.com>
Subject: [PATCH] meta/conf/layer.conf: Avoid adding build deps of rpm-sequoia-native
Date: Mon,  3 Nov 2025 09:04:10 +0100	[thread overview]
Message-ID: <20251103080410.2025712-1-zboszor@gmail.com> (raw)

Avoid adding dependencies of rpm-sequoia-native into sysroots
as it needs none of its build dependencies to run.

It can save significant disk space and speeds up packaging into
signed rpms a little.

It also avoids conflicts with different LLVM/CLANG versions,
like those found in meta-clang-revival.

Signed-off-by: Zoltán Böszörményi <zboszor@gmail.com>
---
 meta/conf/layer.conf | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/meta/conf/layer.conf b/meta/conf/layer.conf
index 54fa04e213..5e78bcfeaf 100644
--- a/meta/conf/layer.conf
+++ b/meta/conf/layer.conf
@@ -116,6 +116,13 @@ SSTATE_EXCLUDEDEPS_SYSROOT += "\
     .*->perlcross-native \
     libarchive-native->e2fsprogs-native \
 "
+# Avoid adding dependencies of rpm-sequoia-native as
+# it needs none of its build dependencies to run.
+# It can save significant disk space and speeds up packaging
+# into signed rpms a little.
+SSTATE_EXCLUDEDEPS_SYSROOT += "\
+    rpm-sequoia-native->.* \
+"
 # Nothing needs to depend on libc-initial
 # base-passwd/shadow-sysroot don't need their dependencies
 SSTATE_EXCLUDEDEPS_SYSROOT += "\
-- 
2.51.0



             reply	other threads:[~2025-11-03  8:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-03  8:04 Zoltán Böszörményi [this message]
2025-11-03 11:16 ` [OE-core] [PATCH] meta/conf/layer.conf: Avoid adding build deps of rpm-sequoia-native Alexander Kanavin
2025-11-03 12:29   ` Böszörményi Zoltán

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20251103080410.2025712-1-zboszor@gmail.com \
    --to=zboszor@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox