From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: [PATCH v5 0/4] Fix cross-build from base-apt when custom DISTRO name used
Date: Tue, 29 Nov 2022 13:20:54 +0100 [thread overview]
Message-ID: <20221129122058.22288-1-ubely@ilbers.de> (raw)
This patchset is mostly intended for downstreams that prefer
renaming DISTRO variable (like `meta-iot2050`) and use
ISAR_CROSS_COMPILE = "1".
This also fixes the case with cross-build on raspberry targets
from cached base-apt repo. While it uses separate repositories
for host (Debian) and target (Raspbian) distros, base-apt is
splittend onto two parts corresponding to the original repos.
Also, testsuite repro tests were updated to cover crosss-build case
and raspberry target is now used in them.
Additionally, download directories for deb packages are now rely
on {HOST_}BASE_DISTRO variables instead of {HOST_}DISTRO.
Changes since v4:
- Normalized download directories (patch 4)
Changes since v3:
- Renamed BASE_HOST_DISTRO to HOST_BASE_DISTRO.
Changes since v2:
- Cleaned garbage in commit message for patch 2.
Changes since v1:
- Support cached cross-build from base-apt for different base distros
for host and target (e.g. raspberry).
Uladzimir Bely (4):
Populate base-apt from both DISTRO and HOST_DISTRO download dirs
testsuite: Run signed repro test in cross mode
testsuite: Replace bananapi with rpi-arm-v7 in signed repro tests
Normalize deb download dirs when custom DISTRO used
meta-isar/conf/distro/raspbian-stretch.conf | 2 +
meta-isar/conf/distro/raspios-bullseye.conf | 2 +
meta-isar/conf/distro/ubuntu-focal.conf | 2 +
meta/classes/dpkg-base.bbclass | 4 +-
meta/classes/dpkg.bbclass | 4 +-
meta/classes/image-tools-extension.bbclass | 4 +-
meta/classes/rootfs.bbclass | 9 ++--
meta/conf/distro/debian-common.conf | 2 +
.../isar-bootstrap/isar-bootstrap.inc | 13 ++++--
meta/recipes-devtools/base-apt/base-apt.bb | 46 ++++++++++---------
.../buildchroot/buildchroot-host.bb | 1 +
.../sbuild-chroot/sbuild-chroot-host.bb | 1 +
testsuite/citest.py | 4 +-
13 files changed, 56 insertions(+), 38 deletions(-)
--
2.20.1
next reply other threads:[~2022-11-29 12:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 12:20 Uladzimir Bely [this message]
2022-11-29 12:20 ` [PATCH v5 1/4] Populate base-apt from both DISTRO and HOST_DISTRO download dirs Uladzimir Bely
2022-11-29 12:20 ` [PATCH v5 2/4] testsuite: Run signed repro test in cross mode Uladzimir Bely
2022-11-29 12:20 ` [PATCH v5 3/4] testsuite: Replace bananapi with rpi-arm-v7 in signed repro tests Uladzimir Bely
2022-11-29 12:20 ` [PATCH v5 4/4] Normalize deb download dirs when custom DISTRO used Uladzimir Bely
2022-12-04 19:06 ` [PATCH v5 0/4] Fix cross-build from base-apt when custom DISTRO name used Jan Kiszka
2022-12-13 12:37 ` 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=20221129122058.22288-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