Re: Accessing sbuild build-directory

[Jan Kiszka <jan.kiszka@siemens.com>]

On 29.05.24 13:24, Anton Mikanovich wrote:
> 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.
> 

"menuconfig" & Co. is just the tip of the iceberg. To really improve
recipe developer life again, full persistent build output is needed.
Because the .config of the one package is the config.h of the other -
you may imagine.

Jan

-- 
Siemens AG, Technology
Linux Expert Center