From: Srinuvasan Arjunan <srinuvasanasv@gmail.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] recipes-devtools/sbuild-chroot: install self-built packages in sbuild flavor
Date: Fri, 15 Dec 2023 03:01:11 -0800 (PST) [thread overview]
Message-ID: <b936a527-9b3a-4032-8ede-eb434e287b11n@googlegroups.com> (raw)
In-Reply-To: <8b19681f-8237-4cef-9235-b6128a37f457@siemens.com>
[-- Attachment #1.1: Type: text/plain, Size: 1318 bytes --]
On Friday, December 15, 2023 at 4:04:49 PM UTC+5:30 Jan Kiszka wrote:
On 15.12.23 10:56, Srinuvasan Arjunan wrote:
> From: srinuvasan <srinuv...@siemens.com>
>
> In some use-cases we need to install custom packages in sbuildchroot and
> this can be referred later time during image generation part, hence we
> need the persistent sbuildchroot rather than the temporary sessions.
We already have a persistent sbuild flavor, but we may lack some
extension to make it usable not only from a package recipe but also an
image recipe. Please work towards that direction.
yes my comment may be wrong, but the intention of the work towards
right directions, this will extend to install the custom packages
in persistent sbuildchroot.
>
> Introduced persistent-sbuildchroot class to handle the above scenarios.
>
> Introduced SBUILD_CHROOT_INSTALL_EXTRA variable, here you can define the
> additional custom packages that you need to install in sbuild flavor.
I don't get the semantic of this variable. We so far have
SBUILD_CHROOT_PREINSTALL, why don't you introduce SBUILD_CHROOT_INSTALL
(SBUILD_CHROOT_PREINSTALL + DEPENDS), analogously to IMAGE_[PRE]INSTALL?
This will address.
Jan
--
Siemens AG, Technology
Linux Expert Center
[-- Attachment #1.2: Type: text/html, Size: 1991 bytes --]
next prev parent reply other threads:[~2023-12-15 11:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 9:56 Srinuvasan Arjunan
2023-12-15 10:34 ` Jan Kiszka
2023-12-15 11:01 ` Srinuvasan Arjunan [this message]
2023-12-15 11:45 ` [PATCH v1] " Srinuvasan Arjunan
2024-01-03 4:47 ` Srinuvasan Arjunan
2024-01-03 5:17 ` Jan Kiszka
2024-01-03 7:56 ` Srinuvasan Arjunan
2024-01-03 10:36 ` Jan Kiszka
2024-01-03 13:11 ` Srinuvasan Arjunan
2024-01-03 16:27 ` Jan Kiszka
2024-01-04 5:43 ` Srinuvasan Arjunan
2024-01-05 12:00 ` Srinuvasan Arjunan
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=b936a527-9b3a-4032-8ede-eb434e287b11n@googlegroups.com \
--to=srinuvasanasv@gmail.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