From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Re: Question related to Sbuild CLEAN_SOURCE
Date: Thu, 10 Feb 2022 10:59:54 +0100 [thread overview]
Message-ID: <YgTiGvxKImUGuEMC@ilbers.de> (raw)
In-Reply-To: <10522aee-53b0-c899-f792-7f83447e35df@siemens.com>
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?
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.
With kind regards,
Baurzhan.
next prev parent reply other threads:[~2022-02-10 9:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1b5ef299-ec8d-c180-c2b6-505294f5484b@siemens.com>
[not found] ` <164435326066.1656.13805705968480410488@localhost>
2022-02-09 10:36 ` quirin.gylstorff
2022-02-09 11:52 ` Baurzhan Ismagulov
2022-02-09 15:14 ` quirin.gylstorff
2022-02-09 15:37 ` Jan Kiszka
2022-02-10 9:59 ` Baurzhan Ismagulov [this message]
2022-02-10 11:27 ` Jan Kiszka
2022-02-10 12:00 ` Baurzhan Ismagulov
2022-02-10 8:47 ` Uladzimir Bely
2022-02-10 9:10 ` quirin.gylstorff
2022-02-11 10:54 ` Uladzimir Bely
2022-02-11 11:20 ` Jan Kiszka
2022-02-14 8:54 ` quirin.gylstorff
2022-02-14 9:47 ` Uladzimir Bely
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=YgTiGvxKImUGuEMC@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