From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] Add PATCHRESOLVE to excluded vars for generating sstate-cache
Date: Fri, 25 Nov 2011 00:04:06 +0000 [thread overview]
Message-ID: <1322179446.10928.41.camel@ted> (raw)
In-Reply-To: <1321569767-21633-1-git-send-email-msm@freescale.com>
On Thu, 2011-11-17 at 16:42 -0600, Matthew McClintock wrote:
> The method of resolving the patch should not effect the sstate-cache
> signature.
>
> Signed-off-by: Matthew McClintock <msm@freescale.com>
> ---
> I'm not 100% sure about this one either - should we even generate
> sstate-cache at all if we have a scenario where we try to resolve
> a patch?
>
> meta/classes/patch.bbclass | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
Merged to master, thanks.
In answer to the question, there clearly shouldn't be a dependency on
this variable. We can depend on the variable even if the conditional
code using it doesn't actually use the code as the dependency analysis
doesn't account for conditional code paths.
Cheers,
Richard
prev parent reply other threads:[~2011-11-25 0:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-17 22:42 [PATCH] Add PATCHRESOLVE to excluded vars for generating sstate-cache Matthew McClintock
2011-11-25 0:04 ` Richard Purdie [this message]
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=1322179446.10928.41.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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