All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-networking][PATCH] networkingmanager: QA warning for rdepends on polkit
Date: Mon, 11 May 2015 21:52:00 +0200	[thread overview]
Message-ID: <20150511195200.GM2400@jama> (raw)
In-Reply-To: <CAMKF1srdavBqMeeuu-FThmD27WsA-Xiirf8KGi24rCMA-J1vgw@mail.gmail.com>

On Mon, May 11, 2015 at 12:43:41PM -0700, Khem Raj wrote:
> On Mon, May 11, 2015 at 12:00 PM, Martin Jansa <martin.jansa@gmail.com> wrote:
> >
> > RDEPENDS adds dependency only between do_package tasks for build time
> > dependency you need do_configure depending on do_populate_sysroot
> 
> its do_build which will depend on do_package_write task in case of RDEPENDS
> and do_package_write task will then recurse further to build it.

        <section id='build-dependencies'>
            <title>Build Dependencies</title>

            <para>
                BitBake uses the
                <link linkend='var-DEPENDS'><filename>DEPENDS</filename></link>
                variable to manage build time dependencies.
                The "deptask" varflag for tasks signifies the task of each
                item listed in <filename>DEPENDS</filename> that must
                complete before that task can be executed.
                Here is an example:
                <literallayout class='monospaced'>
     do_configure[deptask] = "do_populate_sysroot"
                </literallayout>
                In this example, the <filename>do_populate_sysroot</filename>
                task of each item in <filename>DEPENDS</filename> must complete before
                <filename>do_configure</filename> can execute.
            </para>
        </section>


        <section id='runtime-dependencies'>
            <title>Runtime Dependencies</title>

            <para>
                BitBake uses the
                <link linkend='var-PACKAGES'><filename>PACKAGES</filename></link>,
                <link linkend='var-RDEPENDS'><filename>RDEPENDS</filename></link>, and
                <link linkend='var-RRECOMMENDS'><filename>RRECOMMENDS</filename></link>
                variables to manage runtime dependencies.
            </para>

            <para>
                The <filename>PACKAGES</filename> variable lists runtime
                packages.
                Each of those packages can have <filename>RDEPENDS</filename> and
                <filename>RRECOMMENDS</filename> runtime dependencies.
                The "rdeptask" flag for tasks is used to signify the task of each
                item runtime dependency which must have completed before that
                task can be executed.
                <literallayout class='monospaced'>
     do_package_qa[rdeptask] = "do_packagedata"
                </literallayout>
                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.
            </para>
        </section>


so again, RDEPENDS isn't good enough for build time dependencies

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com


  parent reply	other threads:[~2015-05-11 19:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-05  3:18 [meta-networking][PATCH] networkingmanager: QA warning for rdepends on polkit Armin Kuster
2015-05-08 15:12 ` Joe MacDonald
2015-05-08 17:02   ` akuster808
2015-05-08 17:18     ` Joe MacDonald
2015-05-11  9:09 ` Martin Jansa
2015-05-11 18:44   ` Khem Raj
2015-05-11 19:00     ` Martin Jansa
2015-05-11 19:43       ` Khem Raj
2015-05-11 19:46         ` Khem Raj
2015-05-11 19:56           ` Martin Jansa
2015-05-11 19:58           ` akuster808
2015-05-11 19:52         ` Martin Jansa [this message]
2015-05-12  8:53           ` Paul Eggleton

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=20150511195200.GM2400@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.