From: Jan Kiszka <jan.kiszka@siemens.com>
To: Uladzimir Bely <ubely@ilbers.de>,
isar-users <isar-users@googlegroups.com>
Subject: Re: Isar dependency list with sbuild
Date: Mon, 20 Mar 2023 10:22:36 +0100 [thread overview]
Message-ID: <ee99f5fe-d8f1-2146-ca7e-52662c089b0e@siemens.com> (raw)
In-Reply-To: <9513652.eNJFYEL58v@hp>
On 20.03.23 10:00, Uladzimir Bely wrote:
> In mail from Monday, 20 March 2023 10:55:52 +03 user Jan Kiszka wrote:
>> Hi all,
>>
>> just wondering if the list in [1] is still minimal. Specifically, do we
>> still need
>>
>> dpkg-dev
>> git-buildpackage
>> pristine-tar
>>
>> on the host or are those rather installed into the schroot? Same for
>>
>
> We need "dpkg-dev" on host due to `debianize.bbclass` that uses "dpkg-
> parsechangelog" too.
Hmm, if that should really be the only reason to pull dpkg-dev, it would
be a relatively expensive one (about 50MB of deps).
> Other two needs to be checked, probably sbuild don't need
> them on host.
>
>> dosfstools
>> mtools
>> parted
>>
>> I would expect them to be installed into our buildchroot (or soon
>> schroot), rather than being used from the host.
>>
>
> These also need to be checked. They might be needed by wic.
>
The question will be whether this runs inside a chroot or not. But here
we are only talking about 2MB of packages. Still, a shorter list will
always be more handy.
Jan
--
Siemens AG, Technology
Competence Center Embedded Linux
prev parent reply other threads:[~2023-03-20 9:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 7:55 Jan Kiszka
2023-03-20 9:00 ` Uladzimir Bely
2023-03-20 9:22 ` Jan Kiszka [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=ee99f5fe-d8f1-2146-ca7e-52662c089b0e@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.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