public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
To: isar-users@googlegroups.com, Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [PATCH v2] dpkg-base: Drop dependency on buildchroot
Date: Tue, 10 Jan 2023 22:01:35 +0100	[thread overview]
Message-ID: <CAJGKYO7PC2-nM7xu9FndvmWy8x1DAT70dSwP9bvXpEDytJV3oA@mail.gmail.com> (raw)
In-Reply-To: <Y72+ZfeS1Ex96wkj@ilbers.de>

On Tue, 10 Jan 2023 at 20:37, Baurzhan Ismagulov <ibr@radix50.net> 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.
>

So the correct approach could be this one from Jan

https://patchwork.isar-build.org/project/isar/patch/4a89ddd8-5be1-9aff-ab5c-579ecda50b8f@siemens.com/

those who still need buildroot, will simple insert this in their layer

# Add dependency from the correct buildchroot: host or target
do_apt_fetch[depends] += "${BUILDCHROOT_DEP}"

Everybody else will be free by it, per default.

Does it make sense for you?

Best regards, R-

  reply	other threads:[~2023-01-10 21:02 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 [this message]
2023-01-11  6:40   ` Jan Kiszka
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=CAJGKYO7PC2-nM7xu9FndvmWy8x1DAT70dSwP9bvXpEDytJV3oA@mail.gmail.com \
    --to=roberto.foglietta@gmail.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.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