Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Ming Liu <liu.ming50@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] license.bbclass: set do_bootimg recrdeptask on do_populate_lic
Date: Thu, 15 Feb 2018 15:07:20 +0000	[thread overview]
Message-ID: <1518707240.24236.157.camel@linuxfoundation.org> (raw)
In-Reply-To: <CALatG=7Fxnseh+qrNYuO0q85_H7y3eZkv9FaKsMMQ-_819FZvA@mail.gmail.com>

On Thu, 2018-02-15 at 15:11 +0100, Ming Liu wrote:
> I observed this issue on rocko branch, but I think upstream also
> needs it. Since even recrdepends handling had been changed in
> bitbake, the problem here is the "recrdepends" is missing between
> do_bootimg and do_populate_lic, actually there was a bug record for
> it, see: https://bugzilla.yoctoproject.org/show_bug.cgi?id=9446, but
> the fix only considered the missing recrdepends of do_image, but
> looking into get_deployed_dependencies->get_boot_dependencies, the
> do_bootimg also needs a similar fix.

I've looked at this and this patch is not appropriate to be merged, its
a hack, piled on top of other hacks which still don't actually solve
the real problem.

do_bootimg is added before do_image_complete, after do_image, along
with a number of other image processing tasks. Either:

a) license.bbclass requires the do_image dependencies for license
processing.

b) license.bbclass requires the do_image_complete dependencies and
includes the tools used to produce the image.

There is no "in between" state. Creating some kind of mismash of
including some image tasks in the dependency list is simply not
appropriate, its defined as one or the other.

There is already "get_boot_dependencies" in license.bbclass which sets
of alarm bells. Your problem is clearly that you're not getting the
dependencies recursively.

Also, the license deploy manifest creation step is based on do_image
time, *not* do_image_complete. Its thereby defined as the manifest of
the things *in* the image, not the tools used to build the image.
Perhaps it should be at do_image_complete? If it were we might be able
to drop some of these other hacks too...

Cheers,

Richard






  reply	other threads:[~2018-02-15 15:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-15 12:49 [PATCH] license.bbclass: set do_bootimg recrdeptask on do_populate_lic liu.ming50
2018-02-15 13:34 ` Richard Purdie
2018-02-15 14:11   ` Ming Liu
2018-02-15 15:07     ` Richard Purdie [this message]
2018-02-16 12:50       ` Ming Liu

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=1518707240.24236.157.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=liu.ming50@gmail.com \
    --cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox