From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Ming Liu <ming.liu@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/2] sstate: remove binutils-crosssdk from safe dependent list
Date: Tue, 07 Jan 2014 13:58:02 +0000 [thread overview]
Message-ID: <1389103082.6899.27.camel@ted> (raw)
In-Reply-To: <1389082433-19396-2-git-send-email-ming.liu@windriver.com>
On Tue, 2014-01-07 at 16:13 +0800, Ming Liu wrote:
> binutils-crosssdk is being depended by other packages like
> gcc-crosssdk-initial, so it's not safe to be skipped when checking the
> setscene dependencies in setscene_depvalid().
Can you explain this change a bit more please?
Personally, I think the code is right as it is, if the sstate object
exists, it was already compiled and we don't ever need bintuils* so its
a 'safe' dep and can be skipped?
Cheers,
Richard
next prev parent reply other threads:[~2014-01-07 13:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 8:13 [PATCH 1/2] sstate: add do_package to the noexec list in setscene_depvalid Ming Liu
2014-01-07 8:13 ` [PATCH 2/2] sstate: remove binutils-crosssdk from safe dependent list Ming Liu
2014-01-07 13:58 ` Richard Purdie [this message]
2014-01-08 6:05 ` 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=1389103082.6899.27.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=ming.liu@windriver.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