From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: [RFC 0/4] PoC for isar-apt repo reusing
Date: Thu, 2 Sep 2021 11:58:13 +0200 [thread overview]
Message-ID: <20210902095817.32165-1-ubely@ilbers.de> (raw)
Currently, isar-apt repo is always rebuilt at second build when
temporary files except the repo directory were deleted.
This patchset implements proof-of-concept of reusing isar-apt
repo previously built. The idea is to check that package already
exists in the repo and early exit tasks related to fetching/building.
Such approach doesn't remove any tasks from the queue, but changes
their behvaior (early exit) in case of existing package found.
Uladzimir Bely (4):
meta-isar: Fix do_dpkg_build override for prebuild-deb recipe.
isar-apt: PoC of reusing isar-apt repo
ci: Test for isar-apt reuse
doc: Add section for isar-apt reuse functionality
doc/user_manual.md | 23 ++++++
meta-isar/conf/local.conf.sample | 4 ++
.../prebuilt-deb/prebuilt-deb_0.1.bb | 2 +-
meta/classes/dpkg-base.bbclass | 1 +
meta/classes/isar-apt-cache.bbclass | 72 +++++++++++++++++++
scripts/ci_build.sh | 10 +++
6 files changed, 111 insertions(+), 1 deletion(-)
create mode 100644 meta/classes/isar-apt-cache.bbclass
--
2.20.1
next reply other threads:[~2021-09-02 9:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 9:58 Uladzimir Bely [this message]
2021-09-02 9:58 ` [RFC 1/4] meta-isar: Fix do_dpkg_build override for prebuild-deb recipe Uladzimir Bely
2021-09-02 9:58 ` [RFC 2/4] isar-apt: PoC of reusing isar-apt repo Uladzimir Bely
2021-09-02 9:58 ` [RFC 3/4] ci: Test for isar-apt reuse Uladzimir Bely
2021-09-02 9:58 ` [RFC 4/4] doc: Add section for isar-apt reuse functionality Uladzimir Bely
2021-09-02 11:11 ` [RFC 0/4] PoC for isar-apt repo reusing Henning Schild
2021-09-03 8:43 ` Baurzhan Ismagulov
2021-09-03 5:52 ` Jan Kiszka
2021-09-03 8:18 ` Uladzimir Bely
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=20210902095817.32165-1-ubely@ilbers.de \
--to=ubely@ilbers.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