From: Anton Mikanovich <amikan@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>, Claudius Heine <ch@denx.de>,
"Scheler, Fabian" <Fabian.Scheler@siemens.com>,
Uladzimir Bely <ubely@ilbers.de>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: Accessing sbuild build-directory
Date: Wed, 29 May 2024 14:24:43 +0300 [thread overview]
Message-ID: <93d0071c-472d-40ba-b1a3-3d3a69266540@ilbers.de> (raw)
In-Reply-To: <05c5b83c-7ea9-46be-89e8-4d092beb3d08@siemens.com>
28/05/2024 11:52, Jan Kiszka wrote:
> On 28.05.24 10:49, Claudius Heine wrote:
>> Hi Jan,
>>
>> On 2024-05-28 9:58 am, Jan Kiszka wrote:
>>> We should add an option to leave the build artifacts behind when leaving
>>> sbuild, just like we had in the ugly old times with buildchroot. I
>>> wanted to study kernel .config and similar stuff in the past more than
>>> once but always found other ad-hoc workarounds to actually solve that
>>> demand properly.
>> So what are the options for implementing this?
> man sbuild? I don't known, haven't spent time on investigating it, just
> on wanting it.
I was trying --purge* options with sbuild but it didn't work as expected.
Maybe the reason is in schroot managing overlay itself.
As a quick way of handling .config file do_devshell can be used, just
like the
same is done with kernel in yocto.
next prev parent reply other threads:[~2024-05-29 11:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 8:38 Scheler, Fabian (T CED SES-DE)
2024-04-05 9:09 ` Anton Mikanovich
2024-04-05 9:57 ` Uladzimir Bely
2024-04-05 10:03 ` Scheler, Fabian
2024-04-05 13:10 ` Scheler, Fabian
2024-05-28 7:29 ` Claudius Heine
2024-05-28 7:58 ` Jan Kiszka
2024-05-28 8:49 ` Claudius Heine
2024-05-28 8:52 ` Jan Kiszka
2024-05-29 11:24 ` Anton Mikanovich [this message]
2024-05-29 12:33 ` Jan Kiszka
2024-05-29 12:54 ` Baurzhan Ismagulov
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=93d0071c-472d-40ba-b1a3-3d3a69266540@ilbers.de \
--to=amikan@ilbers.de \
--cc=Fabian.Scheler@siemens.com \
--cc=ch@denx.de \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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