public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: [PATCH] dpkg-base: Add devshell_nodeps task
Date: Tue, 2 Nov 2021 09:22:09 +0100	[thread overview]
Message-ID: <cedf18f6-6122-5a00-3493-9c1452c51cb7@siemens.com> (raw)

From: Jan Kiszka <jan.kiszka@siemens.com>

This is useful for debugging dependency issues that apt is usually weak
in presenting clearly. In that case, you may want to beam into the
buildchroot and issue the dependency installation steps manually. The
default devshell is designed to support the build, thus pulls in all
deps first and cannot help here. Therefore this new separate task.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
 meta/classes/dpkg-base.bbclass | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/meta/classes/dpkg-base.bbclass b/meta/classes/dpkg-base.bbclass
index 83500da8..8bbc4165 100644
--- a/meta/classes/dpkg-base.bbclass
+++ b/meta/classes/dpkg-base.bbclass
@@ -269,3 +269,13 @@ addtask devshell after do_prepare_build
 DEVSHELL_STARTDIR ?= "${S}"
 do_devshell[dirs] = "${DEVSHELL_STARTDIR}"
 do_devshell[nostamp] = "1"
+
+python do_devshell_nodeps() {
+    bb.build.exec_func('do_devshell', d)
+}
+
+# devshell may be placed after do_instell_builddeps in downstream classes.
+# devshell_nodeps will always stay right after do_prepare_build.
+addtask devshell_nodeps after do_prepare_build
+do_devshell_nodeps[dirs] = "${DEVSHELL_STARTDIR}"
+do_devshell_nodeps[nostamp] = "1"
-- 
2.31.1

             reply	other threads:[~2021-11-02  8:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-02  8:22 Jan Kiszka [this message]
2021-11-15 11:27 ` Anton Mikanovich

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=cedf18f6-6122-5a00-3493-9c1452c51cb7@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=isar-users@googlegroups.com \
    /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