From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Cc: Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [PATCH 3/4] sdk: Control isar-apt list removing
Date: Thu, 7 Dec 2023 16:46:55 +0100 [thread overview]
Message-ID: <ZXHo7+dlYzQCqvDo@ilbers.de> (raw)
In-Reply-To: <fae5c518-5d93-409b-be7c-0d95be02cd49@siemens.com>
On 2023-12-07 09:55, 'Jan Kiszka' via isar-users wrote:
> > Do not remove isar-apt.list in case SDK_INCLUDE_ISAR_APT enabled.
>
> This says what it does, not why.
>
> Does that isar-apt list really make any sense outside of the build
> environment?
isar-apt is essential for sdk users who have big or complex application
dependencies. It enables hello developer to do apt-get build-dep hello and get
all dependencies installed in the sdk.
This series fixes a regression of an existing feature. The motivation is
described in
https://github.com/ilbers/isar/blob/next/doc/user_manual.md#create-an-isar-sdk-root-filesystem
but the use case could be defined in more specific terms; we'll send a separate
patch for that.
With kind regards,
Baurzhan
next prev parent reply other threads:[~2023-12-07 15:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 12:12 [PATCH 0/4] Fixing isar-apt usage inside SDK Anton Mikanovich
2023-12-06 12:12 ` [PATCH 1/4] rootfs: Split isar-apt and base-apt cleanup Anton Mikanovich
2023-12-06 12:12 ` [PATCH 2/4] sdk: Remove duplicated isar-apt cleanup Anton Mikanovich
2023-12-06 12:12 ` [PATCH 3/4] sdk: Control isar-apt list removing Anton Mikanovich
2023-12-07 0:55 ` Jan Kiszka
2023-12-07 15:46 ` Baurzhan Ismagulov [this message]
2023-12-06 12:12 ` [PATCH 4/4] doc/user_manual.md: Improve SDK usage howto Anton Mikanovich
[not found] <56da6ebc-d264-4cb8-86f9-8b53cbe1212c@ilbers.de>
2023-12-07 15:30 ` [PATCH 3/4] sdk: Control isar-apt list removing Anton Mikanovich
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=ZXHo7+dlYzQCqvDo@ilbers.de \
--to=ibr@radix50.net \
--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