From: Anton Mikanovich <amikan@ilbers.de>
To: Adriaan Schmidt <adriaan.schmidt@siemens.com>,
isar-users@googlegroups.com
Subject: Re: [PATCH] set rdeptask for do_deploy_deb
Date: Thu, 3 Nov 2022 11:54:58 +0300 [thread overview]
Message-ID: <5196937d-f805-e815-48a7-efaff58abf7e@ilbers.de> (raw)
In-Reply-To: <20221025131329.1738241-1-adriaan.schmidt@siemens.com>
25.10.2022 16:13, Adriaan Schmidt wrote:
> Isar currently supports setting build-dependencies between recipes with
> DEPENDS, and runtime/installation dependencies with DEBIAN_DEPENDS.
>
> However, the bitbake mechanism of RDEPENDS, for runtime dependencies
> between recipes, is not supported. So currently, if we model a runtime
> dependecy between recipes, we need to use DEPENDS, which at the same
> time enforces a build dependency, i.e., restricts parallel execution
> of builds.
>
> To enable the use of RDEPENDS in Isar, we set the task (deploy_deb)
> that should be linked by those dependencies.
>
> Signed-off-by: Adriaan Schmidt <adriaan.schmidt@siemens.com>
Applied to next, thanks.
prev parent reply other threads:[~2022-11-03 8:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 13:13 Adriaan Schmidt
2022-11-03 8:54 ` Anton Mikanovich [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=5196937d-f805-e815-48a7-efaff58abf7e@ilbers.de \
--to=amikan@ilbers.de \
--cc=adriaan.schmidt@siemens.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