From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: [PATCH v2 0/1] Improving base-apt usage
Date: Fri, 1 Oct 2021 11:13:28 +0200 [thread overview]
Message-ID: <20211001091329.12979-1-ubely@ilbers.de> (raw)
Changes since v1:
- rebased on latest next
- updated patchset description
Currently, base-apt is used in the following way:
* At first build every deb file that took part in installing is cached in
directory $DL_DIR/deb/. Debootstrap is done from remote source.
* At second build, `base-apt` repo is created from previously downloaded debs
(if ISAR_USE_CACHED_BASE_REPO is set). Debootstrap and installing packages
later is done from this local repo
The idea of this patchset is to precreate `base-apt` at first build and
use it later for all steps. So, no second build will be required.
Currently, only debootstrap part is supported, all build-deps are
still installed as before.
In future, there are plans to switch from debootstrap to mmdebstrap that
is able to work without sudo and uses more clean (apt/python-apt) approach
in comparison with debootstrap.
Uladzimir Bely (1):
[meta] Use cached base-apt repo to debootstrap
meta-isar/conf/distro/ubuntu-focal.conf | 4 +
meta-isar/conf/distro/ubuntu.public.key | 53 +++++
.../isar-bootstrap/isar-bootstrap.inc | 35 ++-
scripts/debrepo.py | 216 ++++++++++++++++++
4 files changed, 307 insertions(+), 1 deletion(-)
create mode 100644 meta-isar/conf/distro/ubuntu.public.key
create mode 100644 scripts/debrepo.py
--
2.20.1
next reply other threads:[~2021-10-01 9:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 9:13 Uladzimir Bely [this message]
2021-10-01 9:13 ` [PATCH v2 1/1] [meta] Use cached base-apt repo to debootstrap Uladzimir Bely
2021-10-05 8:36 ` [PATCH v2 0/1] Improving base-apt usage Henning Schild
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=20211001091329.12979-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