From: Benedikt Niedermayr <benbrenson89@googlemail.com>
To: isar-users@googlegroups.com
Cc: Benedikt Niedermayr <Benedikt.Niedermayr@mixed-mode.de>
Subject: [PATCH v2 7/7] Introducing fetchall, unpackall and unpack_debian tasks.
Date: Thu, 8 Feb 2018 11:40:12 +0100 [thread overview]
Message-ID: <1518086412-12567-8-git-send-email-Benedikt.Niedermayr@mixed-mode.de> (raw)
In-Reply-To: <1518086412-12567-1-git-send-email-Benedikt.Niedermayr@mixed-mode.de>
- fetchall, unpackall:
These tasks offer the possibility for running fetch or unpack tasks for each recipe
in Isar.
After running bitbake "<image>:do_unpackall" Isar will fetch all sources and also unpack them into
related WORKDIRs.
In order to be able to apply the mirror prefetching mechanism, all debian control files must be available
for Isar (Build-Depends required). With all control files available do_cache_config() task should be able to collect
all Build-Depends.
- unpack_debian:
This task should be implemented within each recipe if needed. After the task has run the control file should be located at
${WORKDIR}/${SRC_DIR}/debian/control.
When fetching already debianized sources this task can be omitted.
Locating the control file at the correct position is needed for the dependency collector.
Signed-off-by: Benedikt Niedermayr <Benedikt.Niedermayr@mixed-mode.de>
---
meta/classes/base.bbclass | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
diff --git a/meta/classes/base.bbclass b/meta/classes/base.bbclass
index 7d44f72..5b28707 100644
--- a/meta/classes/base.bbclass
+++ b/meta/classes/base.bbclass
@@ -94,6 +94,26 @@ python do_unpack() {
}
addtask unpack after do_fetch before do_build
+do_unpack[postfuncs] += "do_unpack_debian"
+
+do_unpack_debian() {
+ :
+}
+
+
+addtask fetchall after do_fetch
+do_fetchall[recrdeptask] = "do_fetchall do_fetch"
+do_fetchall[recideptask] = "do_${BB_DEFAULT_TASK}"
+do_fetchall() {
+ :
+}
+
+addtask unpackall after do_unpack
+do_unpackall[recrdeptask] = "do_unpackall do_unpack"
+do_unpackall[recideptask] = "do_${BB_DEFAULT_TASK}"
+do_unpackall() {
+ :
+}
addtask build
do_build[dirs] = "${TOPDIR}"
--
2.7.4
prev parent reply other threads:[~2018-02-08 10:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 10:40 [PATCH v2 0/7] Local apt cache with aptly V2 Benedikt Niedermayr
2018-02-08 10:40 ` [PATCH v2 1/7] Implement support for setting up the local apt mirror and isar repository with aptly Benedikt Niedermayr
2018-02-08 10:40 ` [PATCH v2 2/7] Added API class for apt cache Benedikt Niedermayr
2018-02-08 10:40 ` [PATCH v2 3/7] Added apt-cache functionality for buildchroot Benedikt Niedermayr
2018-02-08 10:40 ` [PATCH v2 4/7] Added apt-cache functionality for image rootfs Benedikt Niedermayr
2018-02-08 10:40 ` [PATCH v2 5/7] Added do_finalize_image task Benedikt Niedermayr
2018-02-08 10:40 ` [PATCH v2 6/7] Added support for installing isar packages to local isar repository Benedikt Niedermayr
2018-02-08 10:40 ` Benedikt Niedermayr [this message]
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=1518086412-12567-8-git-send-email-Benedikt.Niedermayr@mixed-mode.de \
--to=benbrenson89@googlemail.com \
--cc=Benedikt.Niedermayr@mixed-mode.de \
--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