From: Jan Kiszka <jan.kiszka@siemens.com>
To: Srinuvasan Arjunan <srinuvasan_a@mentor.com>,
isar-users@googlegroups.com
Cc: Srinuvasan A <srinuvasan.a@siemens.com>
Subject: Re: [PATCH] doc/user_manual: update Prebuilt .deb packages from somewhere part
Date: Thu, 1 Jun 2023 12:33:13 +0200 [thread overview]
Message-ID: <9edc909d-8010-a711-3aae-f87aa310d90a@siemens.com> (raw)
In-Reply-To: <20230601100753.3523602-1-srinuvasan_a@mentor.com>
On 01.06.23 12:07, Srinuvasan Arjunan wrote:
> From: Srinuvasan A <srinuvasan.a@siemens.com>
>
> When we add prebuilt .deb packages from somewhere, this should be
> install via IMAGE_PREINSTALL not IMAGE_INSTALL, corrected this variable
> name at this chance.
>
> Signed-off-by: Srinuvasan A <srinuvasan.a@siemens.com>
> ---
> doc/user_manual.md | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/doc/user_manual.md b/doc/user_manual.md
> index e07b76d..ada8f9a 100644
> --- a/doc/user_manual.md
> +++ b/doc/user_manual.md
> @@ -906,7 +906,7 @@ from which would be the better way.
>
> Such single debs can be included if need be. You just need to write a recipe
> that just fetches those debs to its `WORKDIR` and deploys them. They can then
> -be installed via `IMAGE_INSTALL`. Have a look at `prebuilt-deb`.
> +be installed via `IMAGE_PREINSTALL`. Have a look at `prebuilt-deb`.
>
No, this is wrong. prebuilt-deb is an own recipe that we need to DEPEND
upon, and that is ensured via IMAGE_INSTALL. IMAGE_INSTALL = DEPEND +
IMAGE_PREINSTALL.
Jan
--
Siemens AG, Technology
Competence Center Embedded Linux
prev parent reply other threads:[~2023-06-01 10:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 10:07 Srinuvasan Arjunan
2023-06-01 10:33 ` Jan Kiszka [this message]
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=9edc909d-8010-a711-3aae-f87aa310d90a@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=srinuvasan.a@siemens.com \
--cc=srinuvasan_a@mentor.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