From: Anton Mikanovich <amikan@ilbers.de>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "Kiszka, Jan" <jan.kiszka@siemens.com>
Subject: [PATCH 3/4] sdk: Control isar-apt list removing
Date: Thu, 7 Dec 2023 17:30:02 +0200 [thread overview]
Message-ID: <f52ec95f-260e-47d0-9807-2ff7a04b28c0@ilbers.de> (raw)
In-Reply-To: <56da6ebc-d264-4cb8-86f9-8b53cbe1212c@ilbers.de>
07/12/2023 02:55, Jan Kiszka wrote:
> This says what it does, not why.
>
> Does that isar-apt list really make any sense outside of the build
> environment?
>
> Jan
I assume saying SDK_INCLUDE_ISAR_APT should actually include isar-apt
into SDK
is not really needed.
You can look into 'Create an ISAR SDK root filesystem' section of
user_manual.md
for outside of the build env example.
next parent reply other threads:[~2023-12-07 15:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <56da6ebc-d264-4cb8-86f9-8b53cbe1212c@ilbers.de>
2023-12-07 15:30 ` Anton Mikanovich [this message]
2023-12-06 12:12 [PATCH 0/4] Fixing isar-apt usage inside SDK 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
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=f52ec95f-260e-47d0-9807-2ff7a04b28c0@ilbers.de \
--to=amikan@ilbers.de \
--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