From: Henning Schild <henning.schild@siemens.com>
To: Uladzimir Bely <ubely@ilbers.de>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH 0/1] Improving base-apt usage
Date: Mon, 13 Sep 2021 11:36:42 +0200 [thread overview]
Message-ID: <20210913113642.0d0c57b7@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20210910153008.16499-1-ubely@ilbers.de>
Am Fri, 10 Sep 2021 17:30:07 +0200
schrieb Uladzimir Bely <ubely@ilbers.de>:
> 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.
Well, in fact you do not need a full second build. Doing so will just
boost confidence that the cache is hopefully complete.
If one does not want to do so, just doing a "bitbake
[mc:<bla>:]base-apt -c do_cache" will be good enough.
Henning
> Currently, only debootstrap part is supported, all build-deps are
> still installed as before.
>
> 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
>
prev parent reply other threads:[~2021-09-13 9:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-10 15:30 Uladzimir Bely
2021-09-10 15:30 ` [PATCH 1/1] [meta] Use cached base-apt repo to debootstrap Uladzimir Bely
2021-09-10 16:43 ` Jan Kiszka
2021-09-13 9:36 ` Henning Schild [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=20210913113642.0d0c57b7@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=ubely@ilbers.de \
/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