public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'MOESSBAUER, Felix' via isar-users" <isar-users@googlegroups.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
	"Kiszka, Jan" <jan.kiszka@siemens.com>
Cc: "cedric.hombourger@siemens.com" <cedric.hombourger@siemens.com>
Subject: Re: [RFC 1/1] speedup localepurge task by emulating less
Date: Mon, 15 Sep 2025 08:23:11 +0000	[thread overview]
Message-ID: <f17dbd52987c0ea86a905065c044c070aba16e0f.camel@siemens.com> (raw)
In-Reply-To: <02cd8640-569d-4eb6-aa8d-57c4f3212628@siemens.com>

On Mon, 2025-09-15 at 08:20 +0200, Jan Kiszka wrote:
> On 21.08.25 17:24, 'Jan Kiszka' via isar-users wrote:
> > On 21.08.25 16:45, Felix Moessbauer wrote:
> > > The download and dpkg status tasks do not need to be emulated, as these
> > > properly support running without a chroot and for a foreign architecture.
> > > 
> > > The install task itself does support running without a chroot, however
> > > not for a foreign architecture. By that, we keep the emulation of the
> > > install task for now.
> > 
> > Can we always parse with older dpkg newer installations? Or does this
> > silently assume that builder-release == target-release then?
> > 
> > To avoid emulation, I would use the dpkg from the host-chroot instead.
> > 
> 
> BTW, with this pattern adjusted, we could also apply it
> rootfs_install_pkgs_download and deb-dl-dir.bbclass.

This is already taken care of by the series "rootfs: introduce wrapper
to run native commands against a rootfs" by Cedric. I anyways propose
to merge his series first and then move on here.

On 20.08.2025 I already sent a ping, but did not get any response.

Felix

> 
> Jan
> 
> -- 
> Siemens AG, Foundational Technologies
> Linux Expert Center

-- 
Siemens AG
Linux Expert Center
Friedrich-Ludwig-Bauer-Str. 3
85748 Garching, Germany

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/f17dbd52987c0ea86a905065c044c070aba16e0f.camel%40siemens.com.

  reply	other threads:[~2025-09-15  8:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-21 14:45 'Felix Moessbauer' via isar-users
2025-08-21 15:24 ` 'Jan Kiszka' via isar-users
2025-09-15  6:20   ` 'Jan Kiszka' via isar-users
2025-09-15  8:23     ` 'MOESSBAUER, Felix' via isar-users [this message]
2025-09-15  8:28       ` 'Jan Kiszka' via isar-users

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=f17dbd52987c0ea86a905065c044c070aba16e0f.camel@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=cedric.hombourger@siemens.com \
    --cc=felix.moessbauer@siemens.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