From: Anton Mikanovich <amikan@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>, isar-users@googlegroups.com
Subject: Re: [PATCH] buildchroot: Add buildchroot dependency for imager
Date: Thu, 8 Jul 2021 15:25:35 +0300 [thread overview]
Message-ID: <0b92d0c1-8284-6f55-6cf9-04918c725a72@ilbers.de> (raw)
In-Reply-To: <9d5d6b80-626c-74ff-bb8c-cd98da1d6a92@siemens.com>
08.07.2021 15:11, Jan Kiszka wrote:
> Right, that would be good. However, the original dependency was omre
> cleanly located than this hack. Why should builchroot know who all
> depends on it?
>
> Jan
>
I also agree that anonymous function is not the right place to control
which buildchroot to use, because it is executed after all other
datastore values are parsed. But this is the place currently, quite a
big rebuild should be done instead.
--
Anton Mikanovich
Promwad Ltd.
External service provider of ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn, Germany
+49 (89) 122 67 24-0
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov
prev parent reply other threads:[~2021-07-08 12:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-07 16:41 Anton Mikanovich
2021-07-08 11:37 ` Jan Kiszka
2021-07-08 11:44 ` Anton Mikanovich
2021-07-08 12:11 ` Jan Kiszka
2021-07-08 12:25 ` 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=0b92d0c1-8284-6f55-6cf9-04918c725a72@ilbers.de \
--to=amikan@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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