From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Ed Bartosh <ed.bartosh@linux.intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v3] image_types.bbclass: get rid of IMAGE_DEPENDS
Date: Fri, 16 Jun 2017 09:52:45 +0100 [thread overview]
Message-ID: <1497603165.24449.6.camel@linuxfoundation.org> (raw)
In-Reply-To: <1497602452-2535-1-git-send-email-ed.bartosh@linux.intel.com>
On Fri, 2017-06-16 at 11:40 +0300, Ed Bartosh wrote:
> The IMAGE_DEPENDS variable can be overriden to add dependencies for
> individual image types. Those dependencies are added to the
> do_rootfs
> task, while they really should be added to the specific image type
> tasks.
>
> Also, the IMAGE_DEPENDS variable is not documented anywhere.
>
> Replaced usage of IMAGE_DEPENDS with explicitly added
> dependencies to do_image_<image type> tasks.
>
> [YOCTO #11302]
>
> Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com>
> ---
> meta/classes/image_types.bbclass | 41 +++++++++++++++++++-----------
> ----------
> 1 file changed, 19 insertions(+), 22 deletions(-)
>
> diff --git a/meta/classes/image_types.bbclass
> b/meta/classes/image_types.bbclass
> index 7749b00..0d7c27e 100644
> --- a/meta/classes/image_types.bbclass
> +++ b/meta/classes/image_types.bbclass
> @@ -29,12 +29,6 @@ def imagetypes_getdepends(d):
> deps = set()
> for typestring in fstypes:
> basetype, resttypes = split_types(typestring)
> - adddep(d.getVar('IMAGE_DEPENDS_%s' % basetype) , deps)
> -
> - for typedepends in (d.getVar("IMAGE_TYPEDEP_%s" % basetype)
> or "").split():
> - base, rest = split_types(typedepends)
> - adddep(d.getVar('IMAGE_DEPENDS_%s' % base) , deps)
You need to do the compatibility checking here I'm afraid
since d.getVar('IMAGE_DEPENDS') is not the same thing
as d.getVar('IMAGE_DEPENDS_%s' % base.
Cheers,
Richard
next prev parent reply other threads:[~2017-06-16 8:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-15 11:59 [PATCH] image_types.bbclass: get rid of IMAGE_DEPENDS Ed Bartosh
2017-06-15 13:25 ` Burton, Ross
2017-06-15 13:27 ` Richard Purdie
2017-06-15 16:19 ` [PATCH v2] " Ed Bartosh
2017-06-15 16:51 ` Leonardo Sandoval
2017-06-15 16:47 ` Burton, Ross
2017-06-15 17:07 ` Leonardo Sandoval
2017-06-16 8:40 ` [PATCH v3] " Ed Bartosh
2017-06-16 8:52 ` Richard Purdie [this message]
2017-06-16 14:15 ` [PATCH v4] " Ed Bartosh
2017-06-16 14:41 ` Richard Purdie
2017-06-16 15:21 ` [PATCH v5] " Ed Bartosh
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=1497603165.24449.6.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=ed.bartosh@linux.intel.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