From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users@googlegroups.com
Subject: Re: [PATCH v2] dpkg-base: Drop dependency on buildchroot
Date: Wed, 11 Jan 2023 07:40:50 +0100 [thread overview]
Message-ID: <6769962e-fa44-fc30-4cc4-359a8f195b3b@siemens.com> (raw)
In-Reply-To: <Y72+ZfeS1Ex96wkj@ilbers.de>
On 10.01.23 20:37, Baurzhan Ismagulov wrote:
> On Tue, Jan 10, 2023 at 08:55:25AM +0100, Jan Kiszka wrote:
>> Neither dpkg_do_mounts nor dpkg_undo_mounts are invoked anymore. Drop
>> them and the whole buildchroot dependency along this.
>
> Yes, we looked at this recently but it was still used in meta-iot2050
> npm.bbclass. Would be good if we could drop it here.
I'm responsible for that use case, so you don't need to worry. And as
long as the buildchroot class itself is not yet gone, we could even keep
it alive in its current form a bit longer. But the right step forward is
to create a dedicated chroot in that class for its npm-fetching use
case. We will deal with that downstream.
Jan
--
Siemens AG, Technology
Competence Center Embedded Linux
next prev parent reply other threads:[~2023-01-11 6:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 7:55 Jan Kiszka
2023-01-10 19:37 ` Baurzhan Ismagulov
2023-01-10 21:01 ` Roberto A. Foglietta
2023-01-11 6:40 ` Jan Kiszka [this message]
2023-01-24 7:37 ` 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=6769962e-fa44-fc30-4cc4-359a8f195b3b@siemens.com \
--to=jan.kiszka@siemens.com \
--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