From: Jan Kiszka <jan.kiszka@siemens.com>
To: Vijai Kumar K <Vijaikumar_Kanagarajan@mentor.com>,
isar-users@googlegroups.com, henning.schild@siemens.com
Subject: Re: [RFC PATCH 0/2] Buildchroot non-determinism
Date: Tue, 30 Nov 2021 17:45:28 +0100 [thread overview]
Message-ID: <4fe6a4e7-22fa-275a-ce92-9f62e62c4c30@siemens.com> (raw)
In-Reply-To: <20211129145241.2932943-1-Vijaikumar_Kanagarajan@mentor.com>
On 29.11.21 15:52, Vijai Kumar K wrote:
> Hello All,
>
> Sometimes buildchroot-host completes long before isar-bootstrap-target
> and proceeds with building packages and populates it in isar-apt.
>
> By the time buildchroot-target is triggered, some packages are available
> via isar-apt and as per the default preference[1], is installed instead
> of the one from other mirrors.
>
> This is not always the case, sometimes there is no such race and the
> packages from DISTRO_APT_SOURCES mirrors are installed.
>
> This makes buildchroot non-deterministic and affects caching.
Just to make the scenario even clearer: This is about packages needed
for the buildchroot-target which happen to be rebuilt by the
buildchroot-host (the other way around is not possible), practically
essential packages that - for whatever reason - requires a rebuild.
>
> One solution is to provide a mechanism to set preferences for
> buildchroot. This way, the user would have flexibility to control the
> mirrors from which certain packages are installed.
>
> This RFC introduces 2 new variables
> 1. BUILDCHROOT_HOST_APT_PREFERENCES
> 2. BUILDCHROOT_TARGET_APT_PREFERENCES
> to set the preferences for buildchroot-host/target respectively.
What is the difference to HOST_DISTRO_APT_PREFERENCES vs.
DISTRO_APT_PREFERENCES? That must be made clear I think.
Jan
>
> Ofcourse, there might be more ways to solve this problem. Happy to
> discuss them here.
>
> Thanks,
> Vijai Kumar K
>
> [1]: https://github.com/ilbers/isar/blob/919fc995fc8ecb675f8bf639ee8628f90728b1ea/meta/classes/rootfs.bbclass#L90
>
> Vijai Kumar K (2):
> meta: Move aggregate_files to base class
> buildchroot: Add provision to specify apt preferences
>
> meta/classes/base.bbclass | 10 +++++++
> .../isar-bootstrap/isar-bootstrap.inc | 10 -------
> .../buildchroot/buildchroot.inc | 30 +++++++++++++++++++
> 3 files changed, 40 insertions(+), 10 deletions(-)
>
--
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2021-11-30 16:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-29 14:52 Vijai Kumar K
2021-11-29 14:52 ` [RFC PATCH 1/2] meta: Move aggregate_files to base class Vijai Kumar K
2021-11-29 14:52 ` [RFC PATCH 2/2] buildchroot: Add provision to specify apt preferences Vijai Kumar K
2021-11-30 16:45 ` Jan Kiszka [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=4fe6a4e7-22fa-275a-ce92-9f62e62c4c30@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=Vijaikumar_Kanagarajan@mentor.com \
--cc=henning.schild@siemens.com \
--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