From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] u-boot-custom: Add control for u-boot-tools package build
Date: Thu, 12 Sep 2019 16:12:12 +0200 [thread overview]
Message-ID: <20190912141212.GI6062@yssyq.m.ilbers.de> (raw)
In-Reply-To: <dad68775-07e4-2499-08ea-e1fefad2105f@siemens.com>
On Tue, Sep 03, 2019 at 07:41:32AM +0200, Jan Kiszka wrote:
> Each custom u-boot currently generates also the u-boot-tools packages.
> That can cause redundant builds in the best case when building multiple
> targets with custom u-boots. In the worst case, an undeterministic
> version is installed, depending one which u-boot with which version is
> finished first.
>
> Allow the user to define which recipe generates also the u-boot-tools
> package so that only one is generated in a multi-target scenario. We
> default to "no build" as a tools package different to the distro one is
> rarely needed on the target.
Applied to next, thanks.
This one is also worth a test case.
With kind regards,
Baurzhan.
next prev parent reply other threads:[~2019-09-12 14:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 5:41 Jan Kiszka
2019-09-12 14:12 ` Baurzhan Ismagulov [this message]
2019-09-13 6:21 ` Jan Kiszka
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=20190912141212.GI6062@yssyq.m.ilbers.de \
--to=ibr@radix50.net \
--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