public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Mikanovich <amikan@ilbers.de>
To: Uladzimir Bely <ubely@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH v5 0/4] Fix cross-build from base-apt when custom DISTRO name used
Date: Tue, 13 Dec 2022 15:37:57 +0300	[thread overview]
Message-ID: <c0b57135-f551-a6aa-3b37-2df5bb60a49b@ilbers.de> (raw)
In-Reply-To: <20221129122058.22288-1-ubely@ilbers.de>

29.11.2022 15:20, Uladzimir Bely wrote:
> 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.

Applied to next, thanks.


      parent reply	other threads:[~2022-12-13 12:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-29 12:20 Uladzimir Bely
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 [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=c0b57135-f551-a6aa-3b37-2df5bb60a49b@ilbers.de \
    --to=amikan@ilbers.de \
    --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