[PATCH] doc: Clarify how task dependencies relate to RDEPENDS

[PATCH] doc: Clarify how task dependencies relate to RDEPENDS

[Jacob Kroon]

Clarify that BitBake knows how to map entries defined in the runtime
dependency namespace back to build-time dependencies (recipes) in
which tasks are defined.

Signed-off-by: Jacob Kroon <jacob.kroon@gmail.com>
---
 doc/bitbake-user-manual/bitbake-user-manual-metadata.xml | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml b/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml
index 10b58835..95a8b95b 100644
--- a/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml
+++ b/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml
@@ -2526,6 +2526,9 @@
                 In the previous example, the <filename>do_packagedata</filename>
                 task of each item in <filename>RDEPENDS</filename> must have
                 completed before <filename>do_package_qa</filename> can execute.
+                Although <filename>RDEPENDS</filename> contains entries from the
+                runtime dependency namespace, BitBake knows how to map them back
+                to the build-time dependency namespace, in which the tasks are defined.
             </para>
         </section>
 

Re: [bitbake-devel] [PATCH] doc: Clarify how task dependencies relate to RDEPENDS

[Denys Dmytriyenko]

On Tue, May 26, 2020 at 09:21:46PM +0200, Jacob Kroon wrote:
> Clarify that BitBake knows how to map entries defined in the runtime
> dependency namespace back to build-time dependencies (recipes) in
> which tasks are defined.
> 
> Signed-off-by: Jacob Kroon <jacob.kroon@gmail.com>
> ---
>  doc/bitbake-user-manual/bitbake-user-manual-metadata.xml | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml b/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml
> index 10b58835..95a8b95b 100644
> --- a/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml
> +++ b/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml
> @@ -2526,6 +2526,9 @@
>                  In the previous example, the <filename>do_packagedata</filename>
>                  task of each item in <filename>RDEPENDS</filename> must have
>                  completed before <filename>do_package_qa</filename> can execute.
> +                Although <filename>RDEPENDS</filename> contains entries from the
> +                runtime dependency namespace, BitBake knows how to map them back
> +                to the build-time dependency namespace, in which the tasks are defined.

That is quite an important clarification!

While working on multiconfig, I faced this issue - I can get build 
dependencies covered by "mcdepends", but there's no way to pull the 
resulting packages into images or SDK, as RDEPENDS or anything that 
results in RDEPENDS (IMAGE_INSTALL, PACKAGE_INSTALL, etc) all trigger 
this build-time dependency namespace check in bitbake and end up in 
errors like "Nothing RPROVIDES <blah>".
I wonder if multiconfig-aware RDEPENDS is needed to bypass this?

-- 
Denys

Re: [bitbake-devel] [PATCH] doc: Clarify how task dependencies relate to RDEPENDS

[Richard Purdie]

On Wed, 2020-05-27 at 16:06 -0400, Denys Dmytriyenko wrote:
> On Tue, May 26, 2020 at 09:21:46PM +0200, Jacob Kroon wrote:
> > Clarify that BitBake knows how to map entries defined in the runtime
> > dependency namespace back to build-time dependencies (recipes) in
> > which tasks are defined.
> > 
> > Signed-off-by: Jacob Kroon <jacob.kroon@gmail.com>
> > ---
> >  doc/bitbake-user-manual/bitbake-user-manual-metadata.xml | 3 +++
> >  1 file changed, 3 insertions(+)
> > 
> > diff --git a/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml b/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml
> > index 10b58835..95a8b95b 100644
> > --- a/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml
> > +++ b/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml
> > @@ -2526,6 +2526,9 @@
> >                  In the previous example, the <filename>do_packagedata</filename>
> >                  task of each item in <filename>RDEPENDS</filename> must have
> >                  completed before <filename>do_package_qa</filename> can execute.
> > +                Although <filename>RDEPENDS</filename> contains entries from the
> > +                runtime dependency namespace, BitBake knows how to map them back
> > +                to the build-time dependency namespace, in which the tasks are defined.
> 
> That is quite an important clarification!
> 
> While working on multiconfig, I faced this issue - I can get build 
> dependencies covered by "mcdepends", but there's no way to pull the 
> resulting packages into images or SDK, as RDEPENDS or anything that 
> results in RDEPENDS (IMAGE_INSTALL, PACKAGE_INSTALL, etc) all trigger 
> this build-time dependency namespace check in bitbake and end up in 
> errors like "Nothing RPROVIDES <blah>".
> I wonder if multiconfig-aware RDEPENDS is needed to bypass this?

Possibly. The challenge is that this RDEPENDS resolution is already
horribly complicated and I'm not sure such dependencies are going to be
at all easy to implement :(.

Cheers,

Richard