From: Anton Mikanovich <amikan@ilbers.de>
To: Florian Bezdeka <florian.bezdeka@siemens.com>,
isar-users@googlegroups.com
Cc: jan.kiszka@siemens.com
Subject: Re: [PATCH] buildchroot: Install ccache into the buildchroot only when enabled
Date: Thu, 23 Jun 2022 21:04:26 +0300 [thread overview]
Message-ID: <0c70182d-584a-4e7c-e787-8c63cc9bfdda@ilbers.de> (raw)
In-Reply-To: <20220610162831.704538-1-florian.bezdeka@siemens.com>
10.06.2022 19:28, Florian Bezdeka wrote:
> This fixes a corner case where the buildchroot is not directly fetched
> from Debian upstream repos but from something like a (manually
> maintained) snapshot. There is no guarantee that the ccache packet is
> available inside the buildchroot packet feed.
>
> As soon as ccache is enabled by setting "USE_CCACHE" to "1" the packet
> will be installed into the buildchroot.
>
> Signed-off-by: Florian Bezdeka <florian.bezdeka@siemens.com>
Applied to next, thanks.
prev parent reply other threads:[~2022-06-23 18:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 16:28 Florian Bezdeka
2022-06-13 7:13 ` Jan Kiszka
2022-06-23 18:04 ` 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=0c70182d-584a-4e7c-e787-8c63cc9bfdda@ilbers.de \
--to=amikan@ilbers.de \
--cc=florian.bezdeka@siemens.com \
--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