Re: Question related to Sbuild CLEAN_SOURCE

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

On 10.02.22 10:59, Baurzhan Ismagulov wrote:
> On Wed, Feb 09, 2022 at 04:37:55PM +0100, Jan Kiszka wrote:
>> Resolving that concrete issue is one thing, but using sbuild in its
>> "convenience feature" mode for Isar is another and not that easily fixable.
> ...
>> What will that mean for layers? Patching Debian packages "ad-hoc" is not
>> an uncommon use case anymore. In fact, bringing Debianization in via
>> Isar/bitbake is even more common and would be equally affected.
> 
> I'm not sure what you mean with "sbuild convenience feature mode", could you
> elaborate a bit?

Read the reply of Josch that Quirin got.

> 
> For layers, I see only advantages. Debian strictly separates source and binary
> packages. We build source packages. sbuild enforces clean-room environment,
> which provides reproducibility through specifying all necessary steps in
> debian/rules.
> 
> Ad-hoc patching and debianization on the fly are not affected; it becomes just
> a matter of providing clean Debian source packages (the state after patching /
> debianization) automatically by Isar.

OK, then we should switch to that and test it. I'd like to see the full
picture, also in context of more layers. It was very helpful, also for
the design discussions, that you converted 2 (besides Isar itself), but
the problem showed up right with the 3rd one.

Jan

-- 
Siemens AG, Technology
Competence Center Embedded Linux