public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Felix Moessbauer <felix.moessbauer@siemens.com>
To: isar-users@googlegroups.com
Cc: jan.kiszka@siemens.com,
	Felix Moessbauer <felix.moessbauer@siemens.com>,
	Adriaan Schmidt <adriaan.schmidt@siemens.com>
Subject: [PATCH] make dpkg-prebuilt task sstate cachable
Date: Fri, 29 Jul 2022 17:50:29 +0200	[thread overview]
Message-ID: <20220729155029.822013-1-felix.moessbauer@siemens.com> (raw)

This makes the dpkg-prebuilt task sstate cachable.
While this is not required in simple situations,
it makes it possible to re-package existing packages
and cache the generated artifacts.

Acked-by: Adriaan Schmidt <adriaan.schmidt@siemens.com>
Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
---
 meta/classes/dpkg-prebuilt.bbclass | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/meta/classes/dpkg-prebuilt.bbclass b/meta/classes/dpkg-prebuilt.bbclass
index 0a6daef7..97e1e2de 100644
--- a/meta/classes/dpkg-prebuilt.bbclass
+++ b/meta/classes/dpkg-prebuilt.bbclass
@@ -1,5 +1,5 @@
 # This software is a part of ISAR.
-# Copyright (C) 2021 Siemens AG
+# Copyright (C) 2021-2022 Siemens AG
 #
 # SPDX-License-Identifier: MIT
 
@@ -16,5 +16,9 @@ python do_unpack_prepend() {
     d.setVar('SRC_URI', ' '.join(src_uri))
 }
 
+# break dependencies on do_patch, etc... but still support sstate caching
 deltask dpkg_build
-addtask unpack before do_deploy_deb
+addtask dpkg_build after do_unpack before do_deploy_deb
+do_dpkg_build() {
+    true
+}
-- 
2.30.2


             reply	other threads:[~2022-07-29 15:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-29 15:50 Felix Moessbauer [this message]
2022-08-05  9:42 ` 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=20220729155029.822013-1-felix.moessbauer@siemens.com \
    --to=felix.moessbauer@siemens.com \
    --cc=adriaan.schmidt@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.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